Spec URL: https://loveshack.fedorapeople.org/review/autoconf268.spec SRPM URL: https://loveshack.fedorapeople.org/review/autoconf268-2.68-1.el6.src.rpm Description: autoconf 2.68 for epel6 Fedora Account System Username: loveshack This provides an updated autoconf for epel6 to support packaging things which need to use autoconf 2.68 after patching their configuration files, e.g. <https://bugzilla.redhat.com/show_bug.cgi?id=1174292>. It's minimally modified from the RHEL autoconf-2.63 packaging, with names by analogy with cmake28 and autoconf213. koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=9037957
Thanks for putting this together. First notes: You should make use of the requires/provides filtering mechanism described here: http://fedoraproject.org/wiki/EPEL:Packaging_Autoprovides_and_Requires_Filtering Drop %defattr() No need for %clean or rm -rf ${RPM_BUILD_ROOT}, or BuildRoot. Otherwise looks good.
I can change it if really necessary, but it has minimal changes from the RHEL source. Why is it worth the effort making it different (not a rhetorical question)? It seems more maintainable if anything to reflect the original.
Because this is a Fedora EPEL package, and I want it to conform to the Fedora EPEL guidelines and not have a bunch of old cruft in it.
I made the changes, though I must say it seems at best a waste of effort. I didn't change the version for cosmetic spec mods.
Looks good, thanks. I would have preferred bumping release, but I think you're already aware of what a stickler I am. One other suggestion: %check # Test fails: 205: parallel autotest and signal handling make check VERBOSE=yes || : this would allow the tests to be logged in the build but not break it. But not a show stopper. APPROVED.
Thanks. I'll make the check change and bump the release. If there's good reason to update release numbers for spec changes in review, perhaps it could be added to the guidelines so it's not just a matter of judgement; I've seen cases where it wasn't done. I'll follow rules of course (preferably with mechanical support).
New Package SCM Request ======================= Package Name: autoconf268 Short Description: A GNU tool for automatically configuring source code Upstream URL: http://www.gnu.org/software/autoconf/ Owners: loveshack Branches: el6
Git done (by process-git-requests).
autoconf268-2.68-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/autoconf268-2.68-2.el6
Well, it was nice thought: autoreconf268: running: aclocal --force -I ../build-config/m4 -I ../vendor/common/build-config/m4 ../build-includes/common.m4:100: error: Libtool version 2.4 or higher is required
(In reply to Orion Poplawski from comment #10) > Well, it was nice thought: > > autoreconf268: running: aclocal --force -I ../build-config/m4 -I > ../vendor/common/build-config/m4 > ../build-includes/common.m4:100: error: Libtool version 2.4 or higher is > required I don't understand. That's not a problem with autoconf, just a requirement of a package.
We're going to need a libtool24 package then as well to make this useful. May want to test this out in a copr before going too far down this road.
(In reply to Dave Love from comment #11) > I don't understand. That's not a problem with autoconf, just a requirement > of > a package. Sorry, I realize it was in reference to #1174292, but I can do libtool if anything else needs it. It's a pity we can't just use the autotools SCL.
autoconf268-2.68-2.el6 has been pushed to the Fedora EPEL 6 testing repository.
autoconf268-2.68-2.el6 has been pushed to the Fedora EPEL 6 stable repository.