From owner-freebsd-questions@FreeBSD.ORG Mon Jul 17 08:45:40 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C387816A4DD for ; Mon, 17 Jul 2006 08:45:40 +0000 (UTC) (envelope-from jsunx1@bellsouth.net) Received: from imf18aec.mail.bellsouth.net (imf18aec.mail.bellsouth.net [205.152.59.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44CF443D45 for ; Mon, 17 Jul 2006 08:45:40 +0000 (GMT) (envelope-from jsunx1@bellsouth.net) Received: from ibm59aec.bellsouth.net ([68.221.117.79]) by imf18aec.mail.bellsouth.net with ESMTP id <20060717084539.HUEO6477.imf18aec.mail.bellsouth.net@ibm59aec.bellsouth.net> for ; Mon, 17 Jul 2006 04:45:39 -0400 Received: from localhost ([68.221.117.79]) by ibm59aec.bellsouth.net with ESMTP id <20060717084539.PXYZ19687.ibm59aec.bellsouth.net@localhost> for ; Mon, 17 Jul 2006 04:45:39 -0400 Date: Mon, 17 Jul 2006 04:49:54 -0400 From: J To: freebsd-questions@freebsd.org Message-ID: <20060717084954.GA13341@brokedownpalace> Mail-Followup-To: freebsd-questions@freebsd.org References: <20060714014823.c4d0b759.nick@nickwithers.com> <000f01c6a6ba$6d1d4340$0a10a8c0@holgerdanske.local> <20060714003829.GA27743@brokedownpalace> <44B731D0.90001@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B731D0.90001@infracaninophile.co.uk> User-Agent: Mutt/1.4.2.1i Subject: Re: 6.1-RELEASE-i386 man broken? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 08:45:40 -0000 On 2006-07-14 (Fri) 06:55:28 [+0000], Matthew Seaman wrote: > J wrote: ... > > FreeBSD, recently, as my transported Linux bash configs contained > > MANPATH=$MANPATH:/custom/manpath. What I never figured out was the > > rationale for this. Anyone mind me asking what's wrong with MANPATH or > > why manpath.config is exclusively favored? For instance, while I have a > > /usr/lib/man.conf on my Linux system and can set the default manpath > > there, man happily coexists with any MANPATH. How does one add a custom > > manpath without root privileges? Etc. Just curious; thanks. > > The manpath(1) program is designed to provide standard system-wide > operation of the man(1) command. It covers all of the places the > ports system will put manpages and all of the system manpages. That > is generally sufficient for most sites. > > If you have a customised directory layout and start putting man pages in > unusual places, then you've got two choices. If these oddly located man > pages are for general consumption, then add the appropriate info to > /etc/manpath.config -- by editing that one file you will make those > manpages visible immediately to all users on the system. > > Otherwise if you have your own private stache of manpages you should > set MANPATH in your shell initialization scripts. However, you should > not assume that MANPATH is already set so that you can just append to > it. To get the best of both worlds, set your local $MANPATH based on the > output of manpath(1). For Bourne-type shells, something like: > > MANPATH="${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man" > export MANPATH > > Or to ignore any previous setting of MANPATH in the environment: > > MANPATH="$( unset MANPATH ; manpath ):/foo/bar/man:/baz/quux/man" > export MANPATH > > csh equivalents are left as an exercise for the student. > Thanks for your time and reply. I'm afraid I'm still failing to see the special advantage in the 'MANPATH-produces-warning' method, but I suppose it's a 'when in Rome'. :)