Hi Andrea, I would ofc sponsor this when it is ready to upload.
Wrt to the executable name: have you talked to upstream yet? I'm sure Debian isn't the only distro that has the muon problem, and I'm sure the maintainer would not like to see this program having different names on different distros. Maybe it also makes sense to talk to upstream KDE if they might consider renaming the executable (even though it is dead, I think everyone could tag a minor release with such a change). I think we should definitely avoid that muon has a non-standard binary name. It is used e.g. as meson build files formatter in certain IDE extensions, and they will not be aware of this. Regards, Stephan On Fri, Aug 19, 2022 at 2:00 PM Andrea Pappacoda <and...@pappacoda.it> wrote: > Package: wnpp > Severity: wishlist > Owner: Andrea Pappacoda <and...@pappacoda.it> > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name : muon-meson > Version : git HEAD > Upstream Author : Stone Tickle <lattis at mochiro dot moe> > * URL : https://muon.build > * License : GPL-3.0 > Programming Lang: C > Description : Meson-compatible build system > > muon is an implementation of the Meson build system in c99 with > minimal dependencies. > . > It uses libpkgconf for dependency discovery, and is close to > feature-complete with the core of Meson for C and C++. > > While still not "stable", muon is capable of compiling quite complex C and > C++ > projects, and being written in C99 it can greatly help with > bootstrappability > when compared to Meson's dependency on a Python interpreter and standard > library. > > The upstream name is "muon", but this package and /usr/bin/ name is already > used by KDE Muon, a [dead] synaptic alternative. > > I'm not sure how to handle this conflict; naming the Debian package "muon- > meson" or "muon-build" seems fine, but renaming the "muon" binary might be > less > desirable. > > [dead]: https://www.reddit.com/r/kde/comments/wrnuq3/is_muon_dead/ > >
