huh? A package that installs files into /usr/lib/perl5/perl_vendor/5.28.1 only works together with perl 5.28.1 - so this package by its pure nature requires perl 5.28.1 - which is exactly what the perl_requires macro adds here. Anything else is nonsense and makes the package broken whenever the perl version changes. On Thu, 2019-10-31 at 03:51 -0700, L A Walsh wrote:
On 2019/10/31 02:27, Dominique Leuenberger / DimStar wrote:
Yet, all perl modules are being installed in /ust/lib/perl5/vendor_perl/<perlversion> - and perl forgets to look in all other locations.
that alone is the reason for the perl modules to require the explicit perl version - or perl actually does not find the modules.
---- Actually, your conclusion is exactly opposite of what is so.
If perl only looked in the new location there would be no reason for a binary check. I.e. if, as you say, perl forgets to look in all other locations, that alone is a reason to NOT include a perl version in the modules because those modules with 'wrong versions' will never be found.
If perl only looks in the new location, then what possible reason would there be to force the packages to have a version in the binary.
Cheers, Dominique
Based on Dominique's observation putting versions in perl and the perl modules is redundant and can only introduce conflict or confusion as perl will only ever look in the appropriately versioned directory.
Therefor I'd like to see a change-action done to have the "requires perl version" removed from rpms and included binary objects.