Follow-up Comment #1, sr #111195 (group libtool): [comment #0 original submission:] > Can we move this script to the libtool project, so that it would be > distributed as $(prefix)/bin/libtool-next-version ? Also, it would be nice if > the doc node "Updating version info" would reference this script.
I can update the documentation to suggest usage of the libtool-next-version
script, but is it preferable for libtool to distribute the script? I am
wondering why it should be moved from gnulib to libtool. It could probably be
incorporated with the gnulib submodule rather than existing in the libtool
repository. Could you supply a patch for how you intend libtool to distribute
the script?
Here is what I have for the documentation updates, but I would be happy to
update with more detail or an example use case:
diff --git a/doc/libtool.texi b/doc/libtool.texi
index 21bb8908..971f5820 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -3222,6 +3222,11 @@ to 0.
In the above description, @emph{programs} using the library in question
may also be replaced by other libraries using it.
+To lessen mistakes when versioning a shared library, you can use the
+@code{libtool-next-version} script authored in gnulib to guide you
+with questions and to simplify the process by supplying default answers
+based on the set of symbols exported by the shared library.
+
@node Release numbers
@section Managing release information
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111195>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
