[Rpm-maint] [rpm-software-management/rpm] Build-id in RPM (Discussion #2031)

[Simo Sorce]

On Sat, 2022-04-23 at 05:14 -0700, Colin Walters wrote:
> > numerical build id - a monotonically increasing build number, 
> 
> That already exists - it's the build time!
> 
> A mode where RPM completely ignores the EVR and simply compares build
> times would help unlock a whole bunch of things, including making it
> easier to [revert to a previous
> version](https://lwn.net/Articles/513346/).

Time could be used, but we need a the same build Id for all the rpms
generated by the build for all arches.
So we can't just use the build time of the individual RPM.

> 
> > and buildtime is hardly a solution for that either.
> 
> Why do you say that?
> 
> That's how ostree works for example today - the version number is
> just for humans, and the code instead just cares about (by default) a
> monotonically increasing timestamp:
> https://github.com/ostreedev/ostree/blob/98587a72db9b52eee63b4bfa9c47a77d2e327501/src/libostree/ostree-repo-pull.c#L1668

This could cause issues if two builders have a time offset or package
building races and any number of other things.

Time *can* be used, when set in stone at SRPM creation time perhaps,
but it is not the only or best option, especially for build systems
that do not forcibly re-create the SRPM.

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc






-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2031#discussioncomment-2629400
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/2031/comments/2629400 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220425/102eadc5/attachment.html>