Keith M Wesolowski wrote: >On Tue, Apr 18, 2006 at 02:07:16PM -0700, Christopher D. Quenelle wrote: > > > >>I replied to this once using email, but I think it is stuck in the >>approver's inbox. The short answer is we might do something like >>make /usr/compilers a link similar to /usr/java. But I agree with >>Rainer about the evilness of the environment selecting which build >>tools are used. If we created /usr/compilers, then the /bin symlinks >>would go through /usr/compilers. If people wanted to they could >>remove the /bin symlinks and add /usr/compilers to their path. Or >>just add /opt/XXX to their path. >> >> > >Here's a revolutionary idea: stop treating every compiler release as a >Major Release and breaking compatibility. The compiler becomes a >synchronously-released part of the operating system rather than an >add-on product, and installs once into /usr/bin. Users won't need >different versions since they'll be compatible. > > > Is it revolutionary? Sounds like going back to SunOS days where the C compiler was bundled. New users still ask "where's the compiler?". Currently the only answer is /usr/sfw/bin/gcc or download and install Sun Studio, which in my opinion, gives the wrong impression.
Now that the Studio tools are free, is there any compelling reason why they can't be bundled? Then we could get rid of the ever confusing /usr/ucb/cc and save Usenet bandwidth. Ian. _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
