[Rpm-maint] [rpm-software-management/rpm] Merge common, important brp-scripts from distros (#419)

Jeff Johnson notifications at github.com
Tue Mar 27 18:28:19 UTC 2018


Some thought ought to be put into how rpm-extras can be merged seamlessly with rpm.

One obvious approach would be to extend the default -> per-machine -> per-packager rpm configuration paradigm with a per-distro (I.e. rpm-extras) stage. In fact, the per-machine configuration layer could be used for rpm-extras (except every distro I am aware of has chosen to patch rpm defaults instead of using per-machine).

Other attempts to break out per-vendor configuration like redhat-rpm-config have been moderately successful, but demonstrated a need for per-platform and cross-compilation.

There have also been attempts like --predefine to force an earliest possible CLI option, rather than inheiritance based, configuration overrides.

There are also current efforts at IDENTITY proofs of reproducible builds, which (at least so far as reproducible packaging is concerned) are most definitely going to be affected by how rpm is configured.

History shows that consensus (wrto rpm configuration mechanisms) is mostly futile. But perhaps rpm-extras might lead to Newer! Better! Bestest! Rpm packaging.

-- 
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/419#issuecomment-376627724
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180327/af997756/attachment.html>


More information about the Rpm-maint mailing list