On Tue, Aug 13, 2024 at 03:59:56PM -0600, Jerry James wrote: > On Tue, Aug 13, 2024 at 11:21 AM Link Dupont <link@xxxxxxxxxxx> wrote: > > 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 > > I agree with Marcus that (1) should not be done. You can't do (1) in > any case. The package has been retired for so long that a review is > required to reactivate the Rawhide branch. See > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming. > > On the other hand, I prefer (2) in this case. The original package > with that name has been gone for so long that I don't see any harm in > repurposing it. That would keep the package name and the upstream > name in sync. Yep, (2) is the best option. After the review is approved, have releng give ownership of the repo to you, and just do a commit that replaces the existing contents. (We have a general rule that commits in dist-git cannot be removed. Thus, the existing content needs to be preserved.) Zbyszek -- _______________________________________________ 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
