[Rpm-maint] [rpm-software-management/rpm] RFE: Store built binary rpms info in source rpm (#642)

[Panu Matilainen]

After thinking about it a bit more over breakfast, there are multiple scenarios that people might want to use that information for. In addition to name, EVR should certainly be included, because it can vary between subpackages. Ditto with arch. Storing the generated binary package name is one straightforward option, all it needs is one new string array tag (provides doesn't seem right for the purpose for several reasons). The obvious downside is that you need to parse the string to access individual components, and it doesn't normally include epoch which you'd probably want to know. The other option would be to add separate name, evr and arch tags for the purpose, which is added complexity and you might still need to parse the evr into its sub-components.

In the meanwhile I remembered the reverse version of this RFE: to include source package NEVR in the binaries (https://bugzilla.redhat.com/show_bug.cgi?id=1008387). That shares the same problems as using the actual binary name would have - the binary name is configurable and thus not reliable, and normally doesn't include epoch at all. 

If we add one, I think we should add the other one too, and sharing the same predictable format.
Parsing these things is not rocket science and everybody does it already anyway so I suppose the single tag variant would do fine as long as it's something that can be reliably parsed. NEVRA seems like an obvious choice but I could be convinced otherwise.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/642#issuecomment-472348979
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190313/44c5aafb/attachment.html>