[Rpm-metadata] Zero epoch vs no epoch (patch)
Christoph Thiel
cthiel at suse.de
Mon May 8 13:51:53 UTC 2006
On Mon, 8 May 2006, Jeff Johnson wrote:
> >I just went through the code of rpm 4.4.5 with our RPM maintainer again
> >and we found:
> >
> >rpmVersionCompare (psm.c):
> >=> no epoch is smaller than epoch 0
> >
>
> rpmVersionCompare is old (and broken).
>
> There are two uses in rpmlib, both tainted with legacy.
>
> One use case is --freshen, which is left exactly as it always has been.
>
> The other use is determining "identical" headers where the header SHA1 is
> compared before EVR, and the SHA1 comparison invariably determines whether
> 2 headers are exactly identical no mater what EVR is present.
>
> >rpmdsCompare(rpmds.c)
> >=> no epoch is equal to epoch 0
> >
>
> rpmdsCompare is the current paradigm, missing epoch is exactly 0, used
> everywhere consistently,
> and its behavior is described as
> Missing or non-specified epoch is treated exactly as Epoch: 0 is.
>
> So what's your issue? Presumably with something other than rpm itself.
I don't have an issue with this at all ;)
Regards
Christoph
More information about the Rpm-metadata
mailing list