On Thu, Jan 22, 2009 at 10:40:44AM -0800, Chris Quenelle wrote: > Danek Duvall wrote: > > My suggestion was that exposing /usr/compilers (and /usr/compilers/bin) > > is unnecessary, since the project's interfaces will be delivered in > > /usr/bin, the need to choose another version of the product can be done > > by modifying $PATH to point first at one of the unbundled > > installations. > > In theory you are correct. But these tools are (for now) living a dual > life. There are utilities and executables that we make available in our > unbundled product that are part of the packages we deliver for the core > tools, but which might not appropriate for putting on the user's default > path. (The 'version' command is the poster child for this.) So there > might be things in /usr/compilers/bin that some people might want to run > sometimes, but we wouldn't want to have symlinks for them in /usr/bin. > This is a wart, and I don't expect many people will ever care enough to > add /usr/compilers to their search path for this reason. But technically > /usr/compilers/bin is not completely an internal directory.
Okay; I was expecting something along those lines, but hadn't heard it yet. Thanks, Danek
