[blfs-dev] [lfs-book] r10418 - branches/systemd/BOOK/chapter06

Bruce Dubbs bruce.dubbs at gmail.com
Fri Dec 27 09:26:23 PST 2013

Armin K. wrote:
> On 12/27/2013 05:43 PM, Bruce Dubbs wrote:
>> Armin K. wrote:
>>> On 12/27/2013 05:23 PM, Bruce Dubbs wrote:
>>>> krejzi at higgs.linuxfromscratch.org wrote:

>>>>>     <screen><userinput remap="configure">./configure --prefix=/usr   \
>>>>>                 --with-readline \
>>>>> +            --infodir=/usr/share/info \
>>>>>                 --mandir=/usr/share/man</userinput></screen>
>>>>>         <variablelist>
>>>> Armin,
>>>>      I'm curious. Why did you add the infodir and mandir switches?  On my
>>>> test build of trunk yesterday, both the man page and the info page were
>>>> placed in the correct place without them.

>>> Not here. They were installed in /usr/man and /usr/info, respectively.
>> You must not have the same directory setup.  In trunk we do:
>> for dir in /usr /usr/local; do
>>     ln -sv share/{man,doc,info} $dir
>> done

> See ncurses and bzip2 instructions. The mandir locations are overriden
> for the very same reason - /usr/info and /usr/man are part of old fhs
> standard and should really go away. We are probably the last
> distribution that still keeps the symlinks. My plan was to remove it in
> not so distant future, but I need to check BLFS first (I've done most of
> it, though) in order to completely nuke it.
> And for those who use package management, packages will install to
> /usr/man *directory* when using destdir method, but since it is a
> symlink, you can't correctly install it using some packaging method.
> Same goes for lib64 -> lib symlink. You might notice that I've overriden
> some blfs packages not to install anything into /usr/lib64 or /lib64 and
> that's for the very same reason (not to write over symlinks).

OK.  For trunk, I really don't see a problem keeping the symlinks for 

   -- Bruce

More information about the blfs-dev mailing list