Packages install non-english man pages in /usr/share/man
richard at reika.demon.co.uk
Tue Jul 17 22:04:39 PDT 2001
Systems which use a unique language and code set for all manual pages
may omit the <locale> substring and store all manual pages in <mandir>.
For example, systems which only have English manual pages coded with
ASCII, may store manual pages (the man<section> directories) directly in
/usr/share/man. (That is the traditional circumstance and arrangement,
So you can make a single language FHS compliant system by
deleting all the other languages.
I used to use a mixture of configure, config.site and configure
options to get all the man pages from /usr/man to /usr/share/man.
This meant my scripts sometimes broke when a pacakage had its
manpage installation fixed. If you use this sort of trick to get
manpages into /usr/share/man/en/, you are going to end up with
paths like /usr/share/man/en/fr_FR/man1/ when the package starts
to support locales properly.
My current solution is to used DESTDIR for everything, and then
move any offending man or info pages before copying to $LFS.
This gets you lots of other advantages, but would be an extra
layer of confusion for new LFS'ers.
I vote for doing nothing until man supports the new directory
layout, then a note near the end of the book like:
For make the man pages fully FHS compliant, edit /usr/share/misc/man.conf
to default to /usr/[local/]share/man/en when /usr/[local/]share/man/<locale>
is not present, then:
mkdir /usr/share/man/en/ /usr/local/share/man/en/
mv /usr/share/man/man[0-9] /usr/share/man/en/
mv /usr/local/share/man/man[0-9] /usr/local/share/man/en/
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the lfs-dev