Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-21 Thread Andrea Pappacoda
Il giorno ven 19 ago 2022 alle 14:43:27 -07:00:00, Russ Allbery ha scritto: Debian specifically disallows providing the same binary path from multiple packages in cases where the two binaries do not do the same thing with roughly the same arguments [1]. It would create a situation where

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Russ Allbery
Andrea Pappacoda writes: > Would alternatives really be that bad? What if the current /usr/bin/muon > was moved to /usr/bin/muon-kde, muon-build was installed to > /usr/bin/muon-build and /usr/bin/muon was shared between the two > packages? What issues could it cause? Debian specifically

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Vincent Bernat
On 2022-08-19 23:14, Andrea Pappacoda wrote: Would alternatives really be that bad? What if the current /usr/bin/muon was moved to /usr/bin/muon-kde, muon-build was installed to /usr/bin/muon-build and /usr/bin/muon was shared between the two packages? What issues could it cause? I don't

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Andrea Pappacoda
Il giorno ven 19 ago 2022 alle 18:51:31 +01:00:00, Simon McVittie ha scritto: I'm not Paul, but I suspect he was looking at Policy ยง10.1: Two different packages must not install programs with different functionality but with the same filenames. (The case of two programs having

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Paul Gevers
Hi, On 19-08-2022 18:10, Luca Boccassi wrote: On Fri, 19 Aug 2022 at 16:54, Paul Gevers wrote: On 19-08-2022 17:41, Luca Boccassi wrote: And if KDE Muon is indeed dead, simply having a "Conflicts: muon" and using the same path should be ok as well? No. Care to elaborate a little?

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Simon McVittie
On Fri, 19 Aug 2022 at 19:19:25 +0200, Andrea Pappacoda wrote: > > And if KDE Muon is indeed dead, simply having a "Conflicts: muon" and > > using the same path should be ok as well? > > I had the same idea, even if it is not extremely elegant. But Paul doesn't > seem to agree; why? I'm not

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Luca Boccassi
On Fri, 19 Aug 2022 at 16:54, Paul Gevers wrote: > > On 19-08-2022 17:41, Luca Boccassi wrote: > > And if KDE Muon is indeed dead, simply having a "Conflicts: muon" and > > using the same path should be ok as well? > > No. Care to elaborate a little? Kind regards, Luca Boccassi

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Paul Gevers
On 19-08-2022 17:41, Luca Boccassi wrote: And if KDE Muon is indeed dead, simply having a "Conflicts: muon" and using the same path should be ok as well? No. Paul OpenPGP_signature Description: OpenPGP digital signature

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Luca Boccassi
On Fri, 19 Aug 2022 at 15:48, Simon McVittie 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

Re: Bug#1017716: ITP: muon-meson -- Meson-compatible build system

2022-08-19 Thread Simon McVittie
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"