Darren Reed <Darren.Reed at Sun.COM> wrote:

> /usr/sfw was fairly straightforward - where we installed software that
> was bundled but not part of ON.  This was problematic for many because
> the default paths of various environments do not include /usr/sfw.

For me, it would be important not to confuse /usr/sfw with /usr/gnu
and to only put GNU (FSF) software into /usr/gnu and not arbitrary free
software (even though this software may be under the GPL).

> I'd also like to see some thought given to libraries - is there any
> intention to create a /usr/gnu/lib, how is that inteded to be used
> vs /usr/lib and /lib, etc, discuss shared library names and their
> conflicts, do people need to use LD_LIBRARY_PATH in addition to
> changing PATH, would /usr/gnu/bin/make pull in as/ld from /usr/gnu
> too, link against glibc, etc...

Wouldn't this require to have two different gcc variants on Solaris?

One that uses as/ld and another one that uses gas/gld?

J?rg

-- 
 EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       schilling at fokus.fraunhofer.de     (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily

Reply via email to