branch: development
commit 7e8ae8b3f2cd38a7be0285174103a3a8470eed85
Author: Ileana Dumitrescu <[email protected]>
AuthorDate: Wed Feb 26 21:46:33 2025 +0200
libtool.texi: Update newlines for previous commit
The documentation follows the traditional method of inserting newlines
before the 80 character limit, with a few exceptions. Now, the
documentation will use some semantic newlines, specifically inserting
newlines for clause breaks (commas, semicolons, colons, and so on).
However, it will only break on symbols, instead of also breaking for
phrases, and it will still utilize the 80 character limit should a
symbol break not exist first.
* doc/libtool.texi: Alter line breaks to use partial semantic newlines.
---
doc/libtool.texi | 23 ++++++++++-------------
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/doc/libtool.texi b/doc/libtool.texi
index 2de42b65..710f238f 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -3257,12 +3257,11 @@ It gives a couple of additional explanations and hints.
@end itemize
Before invoking the wizard,
-you need to build and install
-the previous release and the current release candidate of your package
-into different directories.
+you need to build and install the previous release and the current release
+candidate of your package into different directories.
For example, assume the last release was @code{libfoo-1.4.tar.gz},
-and before preparing @code{libfoo-1.5.tar.gz}, your current release candidate
-is @code{libfoo-1.4.99.tar.gz}.
+and before preparing @code{libfoo-1.5.tar.gz},
+your current release candidate is @code{libfoo-1.4.99.tar.gz}.
You build them like this:
@example
$ rm -rf /tmp/prev /tmp/curr
@@ -3290,21 +3289,19 @@ $ libtool-next-version /tmp/prev/lib/libfoo.so
/tmp/curr/lib/libfoo.so
@cindex command options, libtool-next-version
@cindex options, libtool-next-version command
-The @code{libtool-next-version} program
-determines the next version to use for a libtool library.
+The @code{libtool-next-version} program determines the next version to use
+for a libtool library.
It is invoked as follows:
@example
libtool-next-version [@var{option}]... @var{previous-library}
@var{current-library}
@end example
-@var{previous-library} is
-the installed library (in @code{.a} or @code{.so} format)
-of the previous release.
+@var{previous-library} is the installed library (in @code{.a} or @code{.so}
+format) of the previous release.
-@var{current-library} is
-the installed library (in @code{.a} or @code{.so} format)
-of the current release candidate.
+@var{current-library} is the installed library (in @code{.a} or @code{.so}
+format) of the current release candidate.
It accepts the following options:
