On Wed, 2007-01-24 at 17:07 +0100, Joerg Schilling wrote: > 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).
If I understand it correctly you want to put GNU software into /usr/gnu and non-GNU software under /usr/sfw. Then the question is what we will do in case when some non-GNU software (placed in our /usr/sfw) becomes a GNU software? Will we move the software into /usr/gnu or not? > > > 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 > -- Marcel Telka
