Perhaps I shouldn't overload the issue but the other big problem I see with rpm
building is the source of packages. All that `rpm` does is confirm the packages
are installed for building `BuildRequires:` or for installing `Requires:` but a
package name on its own is not helpful as many people may use multiple repos.
`Yum/Dnf` have been able to configure and pull in rpms from external repos
forever, but even if you do that the rpm specfile itself does not designate or
confirm these sources so it may be impossible to reproduce a build as you can
not find the actual rpm that was used for building or is required to install.
When you take into account the mix of RHEL, CentOS, OEL, AlmaLinux, RockyLinux,
SuSE and its derivatives etc this makes package maintenance, and builds or
rebuilds much more complex. This ends up as being quite a mess if you ever
want to build on similar systems (e.g. the RH variants) So having a way of
addressing this better would be an enormous help.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2654#discussioncomment-8721990
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/2654/comments/8721...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
