Vivien Kraus <viv...@planete-kraus.eu> writes: > Dear gnulib people, > > How do you manage the libtool version information for a library using > gnulib? For now, I have it written down explicitly in configure.ac. > Unfortunately, this requires a new commit to bump the numbers before > each release. > > Gnulib provides a script to help update the libtool version > information. Is there a way to involve that script in the "make > release-commit" invocation? It is a little awkward to create a commit > just to bump the libtool version information, or to squash it with the > commit created by "make release-commit". > > My current solution involves a bit of cheating: fix do-release-commit- > and-tag not to complain about a dirty tree, and have the libtool update > already staged when running make release-commit. > > Am I missing something here? How do you update the libtool version > information?
Consider adjusting your habit to update the libtool version directly
AFTER a release instead. I put the following in cfg.mk to make sure I
don't forget this:
sc_libtool_version_bump:
@git diff v$(PREV_VERSION).. | grep '^+AC_SUBST(LT' > /dev/null
Of course, you still have to bump it if you make any API/ABI changes,
but with this approach, you don't need to bump it just before each
release. And you can have the latest released version installed and
co-exist nicely with the development branch too.
/Simon
signature.asc
Description: PGP signature
