🚀 go-pugleaf

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 do things a little differently than CIS @ Ohio State.  We set up
special accounts for large packages (such as Emacs and X) in the
passwd database, each under group "maint".  The *.pawl.rpi.edu domain
and many Suns in the *.its.rpi.edu domain run off of two file servers
which have /appl partitions for applications.  Emacs has its home
directory in /appl/imagine2/emacs.  Besides creating ~emacs/lock, the
directories ~emacs/local and ~emacs/bin were created.  local holds
mostly elisp packages but also has subdirectories for patches and
images (icons).  All bin has in it are emacs, ctags and etags
executables.  A pointer is made in /usr/local/bin to each executable
in ~emacs/bin.  That takes care of Emacs.

The rest of the GNU stuff goes into /usr/local/src/gnu/{grep/gas/etc}/*.
Executables are in /usr/local/gnu-bin.  In cases like grep, where the
name conflicts with existing names, we do not modify the name.  If
people want to use GNU, they put /usr/local/gnu-bin early in their
PATH.  

Dave
--
      tale@rpitsmts.bitnet, tale%mts@itsgw.rpi.edu, tale@pawl.rpi.edu