Nicolas Williams wrote: > On Fri, Dec 19, 2008 at 11:39:01AM -0800, George Vasick wrote: > > We consulted the submitter, Craig Mohrman. The case is stalled in Sun > > legal. Craig agrees with the concept in our proposal of using > > /usr/compilers/... for this and future versions of compilers allowing > > multiple versions to coexist. Users would then control which is the > > default compiler version by which links package is installed. > > Should we have /usr/interpreters too? (And should Perl5, Python, ... > move there?) What about projects that deliver both, interpreters and > compilers (there exist LISPs that do that)? > > BTW, I like the idea of links pkgs for creating defaults in /bin.
I dislike it since it is the reason that some things can only be build with "root" rights anymore (such as all Mozilla.org products) since you have to remove stuff to prevent things like "autoconf" from finding it by default. OkOk, "autoconf" is a problem anyway but the original Unix designers used PATH for propper namespace seperation and the whole Linux-style "dump all things into /bin" made this situation very bad. ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)
