https://bugzilla.redhat.com/show_bug.cgi?id=1629345
Petr Pisar <ppisar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |WONTFIX
Last Closed| |2018-09-17 04:37:16
--- Comment #1 from Petr Pisar <ppisar(a)redhat.com> ---
I'll answer in a reverse order:
The guidelines are about RPM package versions and how they relate to upstream
release versions. It has nothing to do with Perl module versioning that is a
Perl specific matter.
RPM versions 2.04 and 2.4 are equivalent. RPM versions comparator ignores
leading zeros:
$ rpmdev-vercmp 2.04 2.4
2.04 == 2.4
The Encode::Byte $VERSION is defined in the module file like this:
our $VERSION = do { my @r = ( q$Revision: 2.4 $ =~ /\d+/g ); sprintf "%d." .
"%02d" x $#r, @r };
The RPM module versions are generated by parsing the line, while CPAN evaluates
the line. Evaluating a Perl code is expensive and insecure. That's why RPM
dependency generator does report 2.4 while CPAN reports 2.04.
As you know RPM and Perl versions are incompatible. Because RPM versions are
used by RPM, they must obey RPM arithmetic. I have prepared an automatic
normalization of these generated RPM versions so that they provide correct Perl
and RPM values at the same time but that change cannot be applied alone because
the non-normalized version values are used through out hundreds of RPM
packages. These hundreds of packages would have to be adjusted. And last time
I ask Perl packagers about introducing this change, they disapproved it. Hence
the RPM versions are good only for RPM now.
If you want to use Perl module versions for Perl purposes, please use data from
META.json or ask CPAN database instead. This is not currently supported
feature.
Because "2.04" and "2.4" are RPM-equivalent, I'm not going to work
around this
RPM dependency generator deficiency in the perl-Encode package. It would make
it less legible and harder to maintain and that all without any benefit to RPM
package ecosystem.
Instead I will open a request fir RPM dependency generator change the version
retrieval, but don't have high hopes. This is a very conservative part of
packaging.
--
You are receiving this mail because:
You are on the CC list for the bug.