🚀 go-pugleaf

(BTW, gnu.config is really for discussion of the configuration of the
gnu.* sub-Usenet, not for discussion of how to configure GNU software;
just as gnu.test is really for testing the extent and distribution of
gnu.*, not for discussion of testing GNU software.  I've redirected
followups to gnu.utils.bug, which is the closest to what you were
trying to find.)

In article <HAM.89Apr25211501@polya.Stanford.EDU> ham@polya.Stanford.EDU (Peter R. Ham) writes:
   Is there a standard place to install gnu stuff in a Unix file
   system?  Maybe it doesn't matter, but there must be some places
   that are more maintainable than others.  I'm planning to install
   stuff in /usr/local/src/gnu like /usr/local/src/gnu/gcc etc.

   Does this make sens? Where do other people put this stuff?

We put the sources in /usr/local/src/public/gnu, in the midst of the
rest of our source tree.

Binaries go in /usr/local/bin, which most everyone has in their path
ahead of "/usr/ucb:/bin:/usr/bin".  Where names conflict with those of
vendor-supplied programs later in the path, the name is prefixed with
a "g" (e.g.  gnm, gld, gas) so users know for sure what they're
getting.

Libraries go in /usr/local/lib, which ld(1) and gld(1) both have in
their hardwired default LDPATH after /lib and /usr/lib.  For example,
the Info tree lives in /usr/local/lib/emacs/info/*.

Manual pages (when they exist) go in /usr/man/man? rather than
/usr/local/man/man?  because of the proliferation of
manual-page-delivery programs, not all of which respect MANPATH or
MPATH or whatever.

This is, of course, not to be construed as canonical - you asked what
works for us in our environment.  No warranty expressed or implied.
Opening the shrink-wrap obligates you to nothing.  Your mileage may
vary; check with local dealers for rebate options they may offer; tax,
title, and dealer prep extra.  Stand by and remain clear of the TCA.