[Rpm-maint] [rpm-software-management/rpm] RFE: Allow automating %setup arguments (#368)

[Jeff Johnson]

@nim-nim OTOH, note that builds on a public branch (i.e. no authorization), downloaded through https/ssh (so small chance of maliciously modified),  on a tagged/documented check-in located in an upstream VCS repository, are entirely maintainable, as well as being consistent with RPM's goals of "reproducible builds".

Overloading %setup/%patch convolutes a reproducible build with obscure rpm macro configuration.

In fact, many slow-releasing upstream projects are already released through snapshot tar balls as above. The only difference with existing practice in packaging is through conventions in NVR naming to indicate a pre-release, and the tyranny of manually moving, say, a specific checkin forward by editing a maven-like SourceN: URL (as opposed to preparing a pre-release tarball, which can certainly be done already to simplify rpm packaging using %setup without overloading).

But perhaps I misunderstand the goals described here: [https://fedoraproject.org/wiki/Forge-hosted_projects_packaging_automation](url)

-- 
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/368#issuecomment-350579988
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171210/21095071/attachment.html>