Remove endless boilerplate to perform the same steps in each package by just declaring which kind of buildsystem the package uses using the new Autobuild: spec tag.
Autobuild macros are just regular parametric macros which can be invoked manually from specs too, which should help with reuse and handling complicated cases. As such , this will only work for simple and/or "perfect" upstream projects of course. In reality many/most packages need further tweaking in %install or otherwise. Augmenting those (one way or the other) needs to be implemented to make this real-world usable. Add automake upstream amhello-1.0.tar.gz as an test-case of a rather hands-free autobuild. Fixes: #1087 You can view, comment on, or merge this pull request online at: https://github.com/rpm-software-management/rpm/pull/2620 -- Commit Summary -- * Implement autobuild "template" system (prototype) -- File Changes -- M build/parsePreamble.c (9) M build/parseSpec.c (82) M include/rpm/rpmtag.h (1) M macros.in (9) A tests/data/SOURCES/amhello-1.0.tar.gz (0) A tests/data/SPECS/amhello.spec (14) M tests/rpmbuild.at (13) -- Patch Links -- https://github.com/rpm-software-management/rpm/pull/2620.patch https://github.com/rpm-software-management/rpm/pull/2620.diff -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2620 You are receiving this because you are subscribed to this thread. Message ID: <rpm-software-management/rpm/pull/2...@github.com>
_______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
