Hi Jan, Jan Stary wrote on Wed, Oct 13, 2010 at 03:50:29PM +0200:
> The file DOCS/man/en/mplayer.1 from > http://www.mplayerhq.hu/MPlayer/releases/mplayer-export-snapshot.tar.bz2 > translates into a one-header version with 'mandoc mplayer.1' > and produces the repeating headers with 'groff -man -Tascii mplayer.1' > > So perhaps this is about how exactly the mplayer port builds > its manpage(s) from the mplayer.1; it doesn't: the port seems > to simply copy mplayer.1 into man/man1/mplayer.1 > Then, 'man mplayer' displayes the manpage with repeated headers. Yes: grep _build /etc/man.conf And: man man.conf Hopefully, i will manage to switch the default man.conf from groff to mandoc in time for the 4.9 release. > This seems to be the case with all ports I have looked at > (firefox, sox, unzip, ...); unlike the system man pages > (ls, cp, ...) which have a single header. > > The difference seems to be that the system manpages are > precompiled (with mandoc) into e.g. /usr/share/man/cat1/ls.0 > whereas the port manpages are just the groff sources such as > /usr/local/man/man1/mplayer.1 that get rendered online (with groff). Yes, for now. In the future, it may happen that those manuals requiring groff to build will be installed precompiled, too. Such that those ports get a groff build dependency, but not a groff run dependency. We shall see. > Perhaps (someone correct me please) man calls groff on the manpage > sources, who produces the repeating headers; but mandoc does not. Yes, that's what's currently happening. Yours, Ingo
