On Mon, Oct 20, 2008 at 05:03:27PM +0100, Reuben Thomas wrote: > manpath seems always to add paths configured in /etc/manpath.conf, or at > least the mandatory ones, to the manpath first. This means that the > manpath generated is not necessarily in the same order as the user's > PATH.
I do not believe this to be the case. Aside from looking at the get_manpath_from_path function where you can see that it iterates over $PATH first and only then considers mandatory manpath elements, here's a demonstration: $ echo $PATH /home/cjwatson/bin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/sbin:/sbin $ manpath /usr/local/man:/usr/local/share/man:/usr/share/man $ mkdir ~/man $ manpath /home/cjwatson/man:/usr/local/man:/usr/local/share/man:/usr/share/man I have no ~/.manpath, and /etc/manpath.config does not list anything in my home directory. Could you please provide a demonstration of the problem you're encountering? > However, according to bug #384301, this bug is irrelevant until the > manpath order is actually respected. I've just updated that bug report to note that the manpath actually has nothing to do with it; that bug is really caused by incorrect prioritisation of symlink pages. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
