[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1016470: RFP: muon-meson -- an implementation of the meson build system



Control: reopen 1017716
Control: merge -1 1017716
Control: retitle -1 ITP: muon-meson -- Meson-compatible build system
Control: owner -1 !

On Mon, 01 Aug 2022 10:20:43 +0200 Stephan Lachnit <stephanlachnit@debian.org> wrote:
> * Package name    : muon-meson
>   Version         : any
>   Upstream Author : https://git.sr.ht/~lattis/
> * URL             : https://muon.build/
> * License         : GPL v3
>   Programming Lang: C99
>   Description     : an implementation of the meson build system

Hi, I've filled an ITP for muon a few hours ago, without even noticing that you had filled an RFP. I've (tried to) merge the two reports, hope I didn't mess everything up.

/usr/bin/muon is already used by KDE Muon, as I wrote in #1017716, and on debian-devel we've had a short discussion about how the conflict should be handled, but we did not find a solution yet. You can find the two threads here:

1. <https://lists.debian.org/debian-devel/2022/08/msg00147.html>
2. <https://lists.debian.org/debian-devel/2022/08/msg00160.html>

I personally would've liked a `Conflicts: muon`, even if it sucks, because I'd really like to avoid renaming a binary that is meant to be invoked via the terminal. Maybe we could rename both binaries, one to muon-build and the other to muon-kde, and them make /usr/bin/muon configurable via update-alternatives?

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49


Reply to: