The feature of storing the parsed spec may not seem *that* useful if all you
have is mostly "classic", static spec files. But as the general trend is
towards specs where a significant portion of the content is dynamically
generated (whether via complex macros, dynamic spec generation from build
itself etc), it's increasingly important to capture the actual content used for
the build someplace just to be able to answer "what the heck happened". The
src.rpm header was chosen for the reasons in the PR (#2047) but I'd be much
more willing to discuss an option to store it in a different way than just
"disable it".
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2762#issuecomment-1810234739
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2762/c1810234...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
