There are a few reasons why this is not wired into `%include`. The first being
that `%include` includes a file in place and then continues to read, expand and
parse the rest of the file. This is something that just cannot be done
afterwards. All kind of things could change by re-parsing the spec file. This
is a mess we really don't want (and still have with the BuildArch parsing mess).
This solution allows to not list the specparts in the spec file itself. While
this is not a big benefit with the current feature set in the future this may
allow system wide policies to add stuff without the package needing to know -
as is already the case with the debuginfo packages (even if they are
implemented in a different way).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1485#issuecomment-1297275256
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/1485/c1297275...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
