On Fri, 19 Aug 2022 at 15:48, Simon McVittie <s...@debian.org> wrote:
>
> On Fri, 19 Aug 2022 at 13:57:50 +0200, Andrea Pappacoda wrote:
> > 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.
>
> muon-build seems more consistent with its own domain name muon.build, the
> reference meson implementation's domain name mesonbuild.com, and their
> shared dependency ninja being packaged as ninja-build.

And if KDE Muon is indeed dead, simply having a "Conflicts: muon" and
using the same path should be ok as well?

Kind regards,
Luca Boccassi

Reply via email to