-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split Perl dependency generators into a separate repo #2873
Comments
Thanks for going forward with this. Can you add Tina (perlpunk) and me to the new repo, so we can continue there? For openSUSE we're way into switching to the proper perl version system (currently all packages with conflict-free updates in the last year are switched) and will start soon switching all packages (causing version conflicts temporary). It would be a major help when we wouldn't need a temporary step with manual provides to do so. |
FWIW, I think we should follow the Python lead and call it perl-rpm-packaging to allow for all sorts of helper material to live there and not just macros/scripts and the like. A bit of consistency is a nice bonus. Tagging @jplesnik from Fedora side as well. |
And here goes: https://github.com/rpm-software-management/perl-rpm-packaging The rest is up to the Perl community. If/when you need help with permission matters, please file tickets in https://github.com/rpm-software-management/org-admin . |
These are far better maintained by the Perl community, in a repository of their own: https://github.com/rpm-software-management/perl-rpm-packaging Fixes: rpm-software-management#2873
These are far better maintained by the Perl community, in a repository of their own: https://github.com/rpm-software-management/perl-rpm-packaging Fixes: #2873
Split the Perl dependency generators into a separate GitHub repository managed by our organization. This will make it far easier for the community to maintain and is in the spirit of #1607, and more generally, of #2747.
We need to make sure to preserve the git history when migrating it, though.
There are a couple of pending PRs for these Perl scripts that should be migrated to the new repo once it's ready, namely:
The text was updated successfully, but these errors were encountered: