Bundled Compiler Collection [LSARC/2009/017 FastTrack timeout 01/21/2009]

[Douglas Walls]

Danek Duvall wrote:
> On Thu, Jan 15, 2009 at 11:22:29AM -0800, Douglas Walls wrote:
> 
>>> Why /usr/compilers, then, rather than something under /usr/lib/<mumble>?
>> If ARC members recommend we install the bundled compilers in 
>> /usr/lib/<mumble>
>> that is fine by us, it's just a name and a path.  We chose /usr/compilers
>> as it was not clear to us that we want another WOS in /usr/lib.
> 
> I'm not sure that there's any real definition, but /usr/<mumble> seems to
> be used for components which have Public interfaces beneath that directory
> -- their own bin, man, lib, and so forth, which you'd actually put into
> your $PATH, $MANPATH, -L, etc.  If there are no user-serviceable parts
> there, though (or all of the ones you'd want to use are linked into the
> standard places) then /usr/lib/<mumble> seems like the place to go.  But
> others may have a different understanding.

Ah, yes thanks for that clarification.  /usr/compilers has such public
interfaces, i.e. a bin, lib and man directory intended to be placed in $PATH
and $MANPATH when necessary to override whatever the current defaults
are in /usr/bin /usr/man.

> 
> Danek