Ralf Wildenhues wrote:
> [ moving from bug-libtool ]
>
> * Ralf Wildenhues wrote on Thu, Sep 18, 2008 at 07:11:58AM CEST:
>> * Karl Berry wrote on Sat, Sep 06, 2008 at 01:03:44AM CEST:
>>> Perhaps it would be worthwhile creating/installing a man page for
>>> libtool with help2man, as we do for so many other utilities.
>>>
>>> (We just received a bug report on webmasters from a perplexed user.)
>
> Here's a patch. Notes:
>
> * The additional @direntry will cause 'info libtool' to display the
> libtool invocation node, rather than the top. The top can be gotten
> with 'info Libtool'. This has caused confusion in the Autoconf package
> before, where the direntry was subsequently renamed autoconf-invocation.
> Should I rather use libtool-invocation here, too? That would still make
> the note at the end of the man page slightly wrong, but I don't see a
> way to have both.
>
> * The reformatting of the --help output gets better help2man output; it
> seems to like indented option listing. The patch also removes the "When
> reporting a bug, ..." paragraph from the man page. I wasn't sure if
> this is helpful or bad, but before that, the paragraph would end up in
> the wrong section of the manual. OK?
>
> * Changing $PROGRAM in ltmain.m4sh changes --version output from
> | ltmain.sh (GNU libtool 1.3013 2008-09-08) 2.2.7a
>
> to
> | libtool (GNU libtool 1.3013 2008-09-08) 2.2.7a
>
> This also changes headers in the .lo and .la files. Luckily, the
> detection code greps for $PACKAGE ('libtool') rather than $PROGRAM.
>
> * Tested 'make distcheck'. That revealed that it's really necessary
> to add $(srcdir)/ to the man page names. Since source tree files cannot
> depend upon build tree files, the dependencies are upon the respective
> input files, and libtoolize is added to BUILT_SOURCES so that both
> scripts are guaranteed to exist when the man pages are updated.
>
> OK to install and put Karl in THANKS?
I have not applied the patch to check, but doesn't this just give a
manpage with the default --help output, and no information for the
various --mode options?
I would prefer a manpage that documents all the --help output for all
the modes, is there a way to do that? Maybe add a --help-all option and
make help2man use that? (I have zero knowledge of help2man, sorry for
possibly stupid questions).
Peter
--
Peter O'Gorman
http://pogma.com
