From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scc-mailout.scc.kit.edu (scc-mailout.scc.kit.edu [129.13.185.202]) by krisdoz.my.domain (8.14.5/8.14.5) with ESMTP id pBIJ9pOr022789 for ; Sun, 18 Dec 2011 14:09:51 -0500 (EST) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by scc-mailout-02.scc.kit.edu with esmtp (Exim 4.72 #1) id 1RcM7K-0005xk-B2; Sun, 18 Dec 2011 20:09:50 +0100 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RcM7K-0000HC-CC for tech@mdocml.bsd.lv; Sun, 18 Dec 2011 20:09:50 +0100 Received: from hera.usta.de ([172.24.64.3]) by donnerwolke.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RcM7K-0007CY-B3 for tech@mdocml.bsd.lv; Sun, 18 Dec 2011 20:09:50 +0100 Received: from schwarze by hera.usta.de with local (Exim 4.76) (envelope-from ) id 1RcM7K-00048F-7w for tech@mdocml.bsd.lv; Sun, 18 Dec 2011 20:09:50 +0100 Date: Sun, 18 Dec 2011 20:09:50 +0100 From: Ingo Schwarze To: tech@mdocml.bsd.lv Subject: Re: MANPATH and overriding/modifying default paths. Message-ID: <20111218190950.GB28863@usta.de> References: <4EEDFE12.4020702@bsd.lv> <4EEE01E4.9010604@bsd.lv> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EEE01E4.9010604@bsd.lv> User-Agent: Mutt/1.5.21 (2010-09-15) Hi Kristaps, Kristaps Dzonsons wrote on Sun, Dec 18, 2011 at 04:08:20PM +0100: > On 18/12/2011 15:52, Kristaps Dzonsons wrote: >> A while back, I complained to Ingo that MANPATH is heavy-handed: it >> doesn't allow us to modify the default search path (in, e.g., >> /etc/man.conf), but only override it. >> >> He mentioned that in manpath(1) used on systems, MANPATH can modify >> instead of override by placemen to colons. To wit: > Ugh, I obviously shouldn't type so quickly... "the manpath(1) > utility (Mac OS X, FreeBSD, Linux) can modify the default list by > placement of colons". Heh, you are doing that for manpath(1)-based systems only. In that case, i have certainly no objection. Hum, how do we document that, if it is done for manpath(1), but not for man.conf(5)? Not sure, but that's hardly a show stopper, that can certainly be solved. Maybe it might be useful for man.conf(5)-based systems as well. But i'm not really sure; i never needed it, and i'm a bit hesitant to change utilities to use environment variables for yet more functionality. In any case, i'd rather not change the semantics related to man.conf(5) right now, to not interfere with getting apropos(1) ready. We can return to it later, when we want to. Yours, Ingo -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv