[sr #111195] Include libtool-next-version in the libtool distribution

--8323329-1179144589-1740594141=:2854905
Content-Type: TEXT/plain; CHARSET=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: inline

Follow-up Comment #4, sr #111195 (group libtool):=0A=0A[comment #3 comment =
#3:]=0A> Here's a proposed patch that adds the libtool-next-version program=
 to the=0A> libtool package, including documentation.=0A=0AThank you for th=
e patch file! It looks great, but I would make small changes=0Ato the forma=
tting of libtool.texi for when newlines are used. Also, this=0Ascript addit=
ion is definitely worth adding a NEWS entry. I can write something=0Afor it=
 and make the minor documentation changes in a following commit, but if=0Ay=
ou would like to update the patch file, I can wait to apply that instead.=
=0A=0Adiff --git a/doc/libtool.texi b/doc/libtool.texi=0Aindex 2de42b65..05=
2c6fc4 100644=0A--- a/doc/libtool.texi=0A+++ b/doc/libtool.texi=0A@@ -3256,=
14 +3256,11 @@ It prepares default answers, based on the set of=0Asymbols e=
xported by library.=0A It gives a couple of additional explanations and hin=
ts.=0A @end itemize=0A =0A-Before invoking the wizard,=0A-you need to build=
 and install=0A-the previous release and the current release candidate of y=
our package=0A-into different directories.=0A-For example, assume the last =
release was @code{libfoo-1.4.tar.gz},=0A-and before preparing @code{libfoo-=
1.5.tar.gz}, your current release=0Acandidate=0A-is @code{libfoo-1.4.99.tar=
.gz}.=0A-You build them like this:=0A+Before invoking the wizard, you need =
to build and install the previous=0Arelease=0A+and the current release cand=
idate of your package into different=0Adirectories.=0A+For example, assume =
the last release was @code{libfoo-1.4.tar.gz}, and=0Abefore=0A+preparing @c=
ode{libfoo-1.5.tar.gz}, your current release candidate is=0A+@code{libfoo-1=
.4.99.tar.gz}.  You build them like this:=0A @example=0A $ rm -rf /tmp/prev=
 /tmp/curr=0A $ tar xfz libfoo-1.4.tar.gz=0A@@ -3290,21 +3287,19 @@ $ libto=
ol-next-version /tmp/prev/lib/libfoo.so=0A/tmp/curr/lib/libfoo.so=0A @cinde=
x command options, libtool-next-version=0A @cindex options, libtool-next-ve=
rsion command=0A =0A-The @code{libtool-next-version} program=0A-determines =
the next version to use for a libtool library.=0A+The @code{libtool-next-ve=
rsion} program determines the next version to use=0A+for a libtool library.=
=0A =0A It is invoked as follows:=0A @example=0A libtool-next-version [@var=
{option}]... @var{previous-library}=0A@var{current-library}=0A @end example=
=0A =0A-@var{previous-library} is=0A-the installed library (in @code{.a} or=
 @code{.so} format)=0A-of the previous release.=0A+@var{previous-library} i=
s the installed library (in @code{.a} or @code{.so}=0A+format) of the previ=
ous release.=0A =0A-@var{current-library} is=0A-the installed library (in @=
code{.a} or @code{.so} format)=0A-of the current release candidate.=0A+@var=
{current-library} is the installed library (in @code{.a} or @code{.so}=0A+f=
ormat) of the current release candidate.=0A =0A It accepts the following op=
tions:=0A =0A=0A=0A=0A=0A    ______________________________________________=
_________=0A=0AReply to this item at:=0A=0A  <https://savannah.gnu.org/supp=
ort/?111195>=0A=0A_______________________________________________=0AMessage=
 sent via Savannah=0Ahttps://savannah.gnu.org/=0A
--8323329-1179144589-1740594141=:2854905
Content-Type: APPLICATION/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCZ79b3QAKCRCqLAuaBUf3
TkGkAQCl7tKVqrf23z3oUSzpF4t34k4dpTfAD5Y5Uj8cNenkmQEArdc5QuSEIe9d
/8KLh0ZeJUtrZg1Oqbylh/7Rmx/vTwA=
=i3OP
-----END PGP SIGNATURE-----

--8323329-1179144589-1740594141=:2854905--