[Rpm-maint] [rpm-software-management/rpm] Discussion: splitting language specifics out of rpm core (#1199)

[Panu Matilainen]

The subject has been polluting numerous PR's lately, better to have this discussion separately:

We've been on this road for a long time now, starting from rpm 4.9 introducing the "new" drop-in dependency generator enabling generators to live at the source instead of forcing them into rpm. More recently we removed various perl and python macros from rpm in 4.15. What remains is splitting the remaining language specific generators out of rpm (perl, python, ocaml at least), as we firmly believe that these are better served by respective SIGs rather than rpm maintainers who are not familiar with all these languages. Optimally these would live in repositories of their own with their own stewardships, or lacking sufficient community, rpm-extras.

The concerns around splitting to separate repositories relate mostly to users (distros and otherwise) not discovering said repositories. There must be some things that rpm could do to help with that. Starting with the obvious, documentation and links to known repositories, but other ideas are welcome.

-- 
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/issues/1199
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20200428/bebde2c8/attachment.html>