gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

perl: use "MAJOR.MINOR" instead of "Major.Minor", and explain "patch level"

Browse Source 
We are already using "MAJOR" and "MINOR" in OpenSSL, do the same here.

The semantic versioning documentation (https://semver.org/) always use
"patch level", not "Patch level".  But let's explain it a little to
prevent puzzling people.
This commit is contained in:
Xi Ruoyao 2022-12-09 16:05:26 +08:00
parent 4640b37d96
commit 02912947e8
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
chapter08/perl.xml
View File

@ -123,9 +123,10 @@ export BUILD_BZIP2=0</userinput></screen>
<listitem>
<para>These settings define where Perl looks for installed
modules. The LFS editors chose to put them in a directory structure
based on the Major.Minor version of Perl (&perl-version-min;) which
allows upgrading Perl to newer Patch levels (&perl-version;) without
reinstalling all of the modules.</para>
based on the MAJOR.MINOR version of Perl (&perl-version-min;) which
allows upgrading Perl to newer patch levels (the patch level is
the last dot separated part in the full version string like
&perl-version;) without reinstalling all of the modules.</para>
</listitem>
</varlistentry>