Yeah, but that is the hard part - especially if we want to keep the debuginfo
packages as a macro template. Ofc we could just create those packages in C. But
parsing the template macros after build would be closer to the current
implementation. With the current parser this is a hard ting to do. But the
Dynamic Spec feature has patches to make that work.
In addition the `%__spec_install_post` part relies on the decision made by the
`%install` part. So removing the later will require a new solution for the
former. May be looking at the macros and arch is enough and other decisions can
be based on whether debuginfo files were created.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2204#issuecomment-1261886127
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2204/1261886...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
