Re: Use bash patchlevel as part of RPM version?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 21 April 2009, Axel Thimm wrote:
> On Tue, Apr 21, 2009 at 01:56:22PM +0200, Roman Rakus wrote:
> > What about this NEVR: bash-4.0-p16-6.fc11.i586 where p16 stands for
> > patchlevel 16.
>
> You cannot have a hyphen in the version or the release tag, the above
> is malformed.

But without the hyphen it would work for the expected cases, although probably 
not be packaging guidelines "compliant":

$ rpmdev-vercmp 4.0-1 4.0p16-1
0:4.0p16-1 is newer

$ rpmdev-vercmp 4.0p17-1 4.0p16-1
0:4.0p17-1 is newer

$ rpmdev-vercmp 4.0p17-1 4.0.1-1
0:4.0.1-1 is newer

$ rpmdev-vercmp 4.0p17-1 4.01-1
0:4.01-1 is newer

Cases like 4.0a that should be treated as newer than 4.0p* would require 
either use of Epochs or doing something strange like inventing zeros:

$ rpmdev-vercmp 4.0p17-1 4.0a-1
0:4.0p17-1 is newer

$ rpmdev-vercmp 4.0p17-1 4.0.0a-1
0:4.0.0a-1 is newer

$ rpmdev-vercmp 4.0p17-1 4.0.0-1.a
0:4.0.0-1.a is newer

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux