[Rpm-maint] [rpm-software-management/rpm] RFE: set builsubdir to the *first* extracted archive not the last one (#551)

Jeff Johnson notifications at github.com
Thu Sep 27 02:33:15 UTC 2018


First of all, MaximumRPM was written in 1997, not 2000.

Second, the vast majority of packages have no need for a fancier %setup, nor enhancements like %autosetup. Most software has been distributed on the Internet as a tarball that can be downloaded, and most packages do not need anything more than the few lines of shell script that %setup generates to simplify packaging. Sure times have changed since last century: but surely you are not going to question that the dominant paradigm everywhere is a single tar ball, downloaded, and packaged, where %setup is quite adequate to do the job.

Third, bringing up issues like how URL's are represented in a SourceN: directive, and the parsing quirks in rpmbuild, has nothing whatsoever to do with %setup. RPM is not used as a downloader in production at any time this century. Nor is there any code in rpm-4.14 that can parse a URL: a string is passed to curl (or wget) which does the job, nothing more.

Fourth, positing that %setup should work as "people expect it to work" is pure sophistry. Packagers expect %setup to do what it has always done, across 25 years of spec files and packaging. Every change to RPM has a huge ripple effect, the rate of adoption of any change is measured in years or decades, because of promises of long term support in enterprise distro's like RHEL and CentOS.

If you claim otherwise, or think it's time for a change, then by all means get off your bully pulpit and

Show me (and all of us) your code.



-- 
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/551#issuecomment-424936766
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180926/f0514135/attachment-0001.html>


More information about the Rpm-maint mailing list