[Rpm-maint] [rpm-software-management/rpm] Build version (build tag?) in RPM (Discussion #2031)

Miroslav Suchý notifications at github.com
Tue Apr 26 10:56:30 UTC 2022


Random thoughts from me:

* +1 to the idea in general.
* Forget about Koji, Copr. Or OBS. Solve the task on a local level first. I.e. in plain Mock on the command line.
* The filename is already long. And 3rd party users (look into Stackoverflow questions) already use `foo.rpm` removing the VRA from the filename. Not even mention the dist tag.
* On the other hand, make sure that the outcome does not go against idea of reproducible builds.
* The number should be self-explanatory. I.e. when we use disttag fc36 people know what it is. Compared to ID number from the row from PDC.
* Even for automatic rebuilds you may want to know the reason: Rebuild because of new Python. Mass rebuild of all packages (just because). Rebuild because of a new definition of macro X...

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

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


More information about the Rpm-maint mailing list