openssl: reword upgrading note for versioning scheme change

This commit is contained in:
Xi Ruoyao 2022-05-28 21:04:22 +08:00
parent 0ab908d944
commit 0d7dbaf24c
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -81,12 +81,15 @@ make MANSUFFIX=ssl install</userinput></screen>
<note>
<para>
You should update OpenSSL when a new version which fixes vulnerabilities
is announced. The releases run in series, with a letter for each release
after the initial release (e.g. 1.1.1, 1.1.1a, 1.1.1b, etc). Because LFS
installs only the shared libraries, there is no need to recompile packages
which link to <filename class="libraryfile">libcrypto.so</filename> or
is announced. Since OpenSSL 3.0.0, the OpenSSL versioning scheme
follows the MAJOR.MINOR.PATCH format. API/ABI compatibility
are guaranteed for the same MAJOR version number. Because LFS
installs only the shared libraries, there is no need to recompile
packages which link to
<filename class="libraryfile">libcrypto.so</filename> or
<filename class="libraryfile">libssl.so</filename>
<emphasis>when upgrading in the same series.</emphasis>
<emphasis>when upgrading to a version with MAJOR version number
unchanged</emphasis>.
</para>
<para>