> %buildsubdir is a long-standing documented macro, we can't just rename it on
> a whim as doing so will break packages that were doing nothing wrong.
Okay, I didn't realize that, but the renaming part is only there because I
thought the codebase didn't like to expose non-underscored globals. If we're
already documenting it as exposed, doing it without the underscore is just fine
by me. In that case all this does is make it be exposed more like other
variables are.
> What's the actual use-case behind this?
It helps me subclass debuginfo generation on weird platforms and packages that
build for more than one target inside the same build.
--
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/pull/860#issuecomment-535043577
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
