Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!mcnc!duke!bet
From: bet@orion.mc.duke.edu (Bennett Todd)
Newsgroups: comp.sources.d
Subject: Re: man pages - what goes where?
Message-ID: <14818@duke.cs.duke.edu>
Date: 21 Jun 89 19:32:13 GMT
References: <1989Jun19.021419.1512@telly.on.ca> <2115@ucsfcca.ucsf.edu>
Sender: news@duke.cs.duke.edu
Reply-To: bet@orion.mc.duke.edu (Bennett Todd)
Organization: Diagnostic Physics, Radiology, DUMC
Lines: 22
In-reply-to: root@cca.ucsf.edu (Systems Staff)

If you are fortunate enough to be using a system whose man(1) command
knows about the environment variable MANPATH, then you can just put

	MANPATH='/usr/man:/usr/local/man'

(for Bourne style shells) or

	setenv MANPATH '/usr/man:/usr/local/man'

(for C shells) in the same place you add /usr/local/bin to the PATH,
then have a complete heirarchy of /usr/local/man/{man,cat}[1-8]. We do
this, and as as result /usr/local stands independant of the rest of the
system (we also have /usr/local/lib, /usr/local/etc, /usr/local/include,
and /usr/local/src). It sure is nice being able to mount up one
filesystem for everybody, being able to upgrade the OS and leave the
local stuff virtually completely installed, being able to take
/usr/local/src and put it in a new filesystem on a new machine and
rebuild a complete standalone /usr/local tree for that system, and like
that. 

-Bennett
bet@orion.mc.duke.edu