retitle 282725 libtoolize: missing introductory documentation
tags 282725 + upstream
found 282725 libtool/2.4.2-1
# documentation
severity 282725 minor
quit
Hi,
Ross Boylan wrote:
> When attempting to add libtool support to my package I get
> $ libtoolize -n
> libtoolize: `configure.ac' does not exist
> Try `libtoolize --help' for more information.
>
> The --help doesn't provide any more clues.
Hmm. When I try it, "libtoolize" is happy to just do nothing in this
case. I suspect this change occured in release-2-1b~568 ("It's
perfectly fine to run `libtoolize --ltdl --copy' in a tree that has no
configure.ac or configure.in; we want libltdl to be useful even to
projects that don't use autotools themselves.", 2005-08-23).
However, the manpage and --help output are still profoundly
uninformative:
Prepare a package to use libtool.
Likewise, the info page is unhelpful:
The `libtoolize' program provides a standard way to add libtool support
to your package. In the future, it may implement better usage
checking, or other features to make libtool even easier to use.
The `libtoolize' program has the following synopsis:
libtoolize [OPTION]...
and accepts the following options:
By contrast, the gettexize info page explains a little more:
The `gettextize' program is an interactive tool that helps the
maintainer of a package internationalized through GNU `gettext'. It is
used for two purposes:
* As a wizard, when a package is modified to use GNU `gettext' for
the first time.
* As a migration tool, for upgrading the GNU `gettext' support in a
package from a previous to a newer version of GNU `gettext'.
This program performs the following tasks:
[...]
Can you suggest any advice to help people get started using
libtoolize? I'd be happy to help convert whatever text you provide to
a patch for the texinfo manual or the --help output, or to an extra
section included in the help2man conversion process.
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
