This is actually a nice use case to look how to make spec files more
declarative and what road blocks are ahead. The main issue here is that there
are all those moving pieces and rpm is not great in having them all in random
order. Everything needs to go to the right place in the spec and so it is very
difficult to expand this from a single place. Even more so if you what to have
more than one %alternatives line.
So this starts with there only being one %files section per sub package and
only one of each scriptlets and build scripts.
The %post and %postun scripts should actually done with file triggers but it's
hard to pass data to them other than in the files themselves.
May be we need to address them one by one.
--
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/993#issuecomment-580320572
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
