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. > > Danek
I think this is a good guideline. Unfortunately, the current delivery is a strange mix of the two. Once we get our directory structure sorted out (for the unbundled product and the bundled compilers), then I think a lot of our files could go under a /usr/lib subdirectory. --chris
