On Wed, Jan 24, 2007 at 02:31:14PM +0100, Darren Reed wrote:
> I would be tempted to say that the architecture for /usr/gnu should
> be that unless Sun provides a command with a similar name, programs
> should always be installed into /usr/bin, not /usr/gnu/bin, except
> in the case of those with a 'g' prefix - 'g' version in /usr/bin,
> non-'g' version in /usr/gnu/bin.  This way people aren't required
> to modify their default environment in order to access the extra
> tools available.  Otherwise we're just reinventing the /usr/sfw/bin
> problem but with a new name.

I thought the proposal was for pretty much what you suggest.

> 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...

LD_LIBRARY_PATH is not meant for everyday production use.  All ELF
objects we deliver should have proper dependencies recorded and proper
runpaths (ld ... -R ...), so that should not be an issue.

As for gas/gld.  I can't recall ever needing to use those on Solaris.

Nico
-- 

Reply via email to