On Thu, 2019-10-31 at 05:37 -0700, L A Walsh wrote:
On 2019/10/31 03:55, Dominique Leuenberger / DimStar wrote:
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.
---- I think I'm not making myself clear.
When a package is generated for perl 5.28.1, the rpm will include instructions to install it under the perl-lib dir under directory 5.28.1. That would still remain. If you install perl 5.28.2, the new perl won't look in 5.28.1. That won't change.
What is happening now is that when you create the package in ADDITION to what directory it is installing into (5.28.1). The suse build process requires that the rpm also say it is only for 5.28.1, AND if there is any binary, the binary _may_ be marked to only look for a matching perl version of 5.28.1.
It is marked in 3 separate places. The first thing I point out is that 1 is enough -- the fact that it is installed in 5.28.1 means a perl built to only look in 5.28.2 won't see it -- so it is pointless to put the requirement in the rpm and in the binary.
The dep inside the rpm is nescessary for the package to actually TELL the user that this won't work - installing files to a directory where our perl won't look for it is not going to help. I understand YOU might have different requirements. Me though, I'm responsible as Release Manager for a product that works 'for most people without hassle' - I'm fully aware the distro I'm responsible for will never match the requriements of 'all people' (in this case, likely you) - but I'm not willing to give up this dependency in the rpms to cater to your need here. Cheers, Dominique