URL: <https://savannah.gnu.org/support/?111195>
Summary: Include libtool-next-version in the libtool
distribution
Group: GNU Libtool
Submitter: haible
Submitted: Di 25 Feb 2025 10:38:51 CET
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Di 25 Feb 2025 10:38:51 CET By: Bruno Haible <haible>
As maintainer of a package that ships a shared library, it is easy to make
mistakes when assigning a new libtool version triplet, while making a release.
(Doc node "Updating version info".)
To make this process more reliable, there is a program
gnulib/build-aux/libtool-next-version that improves this process
1) by asking the maintainer questions, so that they can focus on one thing at
a time,
2) by giving additional help to the maintainer (for example, by explaining
what constitutes an "interface" of the shared library),
3) by preparing default answers based on the set of symbols exported by the
shared library.
I am using this script for the GNU gettext and GNU libunistring releases of
the last 5 years, and it has avoid a mistake more than once.
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.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111195>
_______________________________________________
Nachricht gesendet über Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
