From 02912947e8a276c61d192157406c7dfb63f048cf Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 9 Dec 2022 16:05:26 +0800 Subject: perl: use "MAJOR.MINOR" instead of "Major.Minor", and explain "patch level" 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. --- chapter08/perl.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'chapter08/perl.xml') diff --git a/chapter08/perl.xml b/chapter08/perl.xml index 112780c4a..b56e0e5e2 100644 --- a/chapter08/perl.xml +++ b/chapter08/perl.xml @@ -123,9 +123,10 @@ export BUILD_BZIP2=0 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. + 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. -- cgit v1.2.3-54-g00ecf