[Rpm-maint] [rpm-software-management/rpm] Embed Build Environment Information into RPM Builds (Discussion #4074)

[Panu Matilainen]

Had a look at the PR and it is useful from the food-for-thought point of view: this isn't how to do it, should we want to store such info in rpms. It'd need a proper plan to start with though.

There have been multiple tickets, discussions and PR's at related items, some of the more interesting ones being https://github.com/rpm-software-management/rpm/discussions/2851 and in particular, https://github.com/rpm-software-management/rpm/pull/1532

The build info should be collected in a form that can be fed into rpmbuild for a rebuild. There are bits and pieces lying around already: the parsed spec exists in the srpm header. The scriptlet environment is exported to a file during a build, and we'll need to dump the entire macro context into a file for #3643. Grand plan is missing though. Whether the src.rpm is the best place to put all this is another question, the -buildinfo binary package has several advantages. 

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

Message ID: <rpm-software-management/rpm/repo-discussions/4074/comments/15997959 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260304/51bbd287/attachment.htm>