Having the utilities to generate these variables shipped with rpm would mean
downstream consumers could use them to generate the macros they desire. For
example Fedora could reuse them to generate python2_* and python3_* etc. I
intend to submit a patch doing exactly that against redhat-config-rpm after
this is merged to upstream rpm (and request adding this change as a patch in
Fedora's rpm package).
FWIW I'm kind of still wondering if it would be better to have only one tool
that would generate these three outputs based on arguments given to it instead
of having three (like they're now in this PR). So e.g. instead of invoking
`%{_rpmconfigdir}/python_sitelib` to get the sitelib, one would do
`%{_rpmconfigdir}/python_something sitelib`. Let me know if you'd like me to do
that, and feel free to suggest names for the combined script.
--
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/221#issuecomment-306799576_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
