On Fri, Aug 14, 2020 at 11:29:14AM +0800, Kevin Buckley via lfs-dev wrote:
>
> The thread explains why the addition of the "perl-version-min"
> subdirectory is required. but why the hard-coding of 5.32
> when that's what the entity value would be expanded to,
> given what's in packages.ent, vis:
>
> <!ENTITY perl-version-major "5">
> <!ENTITY perl-version-minor "32">
> <!ENTITY perl-version-patch "0">
> <!ENTITY perl-version-min "&perl-version-major;.&perl-version-minor;">
>
Yeah, oversight, I mostly touch BLFS these days.
> What happens when Perl5 moves to 5.33, 5.34 later versions?
>
If 5.33 ever happens, then it will be a development version like all
odd-numbered perl5 releases. And if 5.34 happens then (on after an
upgrade) the 5.32 modules already installed should still be found,
which was the point of the initial change.
Of course, with the current plans for perl7 (coupled apparently with
much longer support for 5.32) what will happen in terms of their
releases is not settled. I've seen comments that perl7 will break
CPAN modules.
ĸen
--
Juliet's version of cleanliness was next to godliness, which was to
say it was erratic, past all understanding and was seldom seen.
-- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
