You have chosen rpm spec files and macros for your implementation.
Neither was designed for multiple builds in a single package, nor was rpm for
that matter.
Instead of complaining about rpm deficiencies and quirks, you might wish to
rethink your approach, look at the inputs of archive/patch names, choose
whatever directory hierarchy you wish, and script up your "chained builds" in
whatever programming language you choose.
Then run your "chained builds" within an rpm spec file.
--
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-425629385
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
