The problem is that nothing like this exists in rpm internally. The spec is
such an organigally grown hodgepodge that its simply impossible to impose
structure on where it does not exist.
Having sub-package information in meaningfully accessible data structures
sounds like a job for spec-ng, and actual programming language bindings to it.
This is well beyond what simple macros can or should be able to do.
--
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/573#issuecomment-603304916
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
