Hi Link,
I'll assume there's a precedent for "taking over the name of old packages" (might be just
"you don't"), but even if there wasn't, choice 1) would be strange – it *is* a new
package, so obviously, it should go through the review process.
I'd favor 3) because `ninja-build` already exists, so this isn't a completely new thing
within the realm of build systems, and there will be no need for discussion, nobody
forward-porting something from the old-muon days that conflicts, depends or otherwise
interacts with your new package.
To make that a bit sweeter: Try `dnf5 install gnuradio-companion`. It will ask you to
install the `gnuradio` package. I honestly don't know why – `dnf5 repoquery --whatprovides
gnuradio-companion` comes up empty, but it still works. So, chances are `dnf install muon`
would still install `muon-build`.
Best,
Marcus
On 13.08.24 19:20, Link Dupont wrote:
Hello,
I noticed that the up-and-coming meson-compliant build tool muon[1] is not currently available in Fedora. While searching around, I found that a dist-git repository[2] titled "muon" already exists, and used to contain a KDE Plasma utility. It has been orphaned for a very long time (April 2016). I'm considering submitting muon[1] to Fedora, and I'd like to solicit the community opinion on how to reconcile the package names. I can think of a few approaches to take.
1) Adopt muon[2], package muon[1] and push it to rawhide. YOLO.
2) Adopt muon[2], package muon[1], submit a New Package Review and reconcile the existing dist-git repository with releng when the Review is approved.
3) Package muon[1] under a new package name (muon-build), submit a New Package Review, etc. Include a "Provides" to keep the "muon" name.
Are there any better approaches to take here?
~link
1: https://github.com/muon-build/muon
2: https://src.fedoraproject.org/rpms/muon
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
