Bug#1071383: gnome-core should recommend network-manager instead of network-manager-gnome

[Simon McVittie <smcv@debian.org>]

On Tue, 05 Nov 2024 at 12:05:41 +0000, Mike Gabriel wrote:
> On  Mi 16 Okt 2024 21:00:41 CEST, Michael Biebl wrote:
> > Am 14.10.24 um 17:13 schrieb Simon McVittie:
> > > On Mon, 14 Oct 2024 at 16:33:40 +0200, Michael Biebl wrote:
> > > > The name of the network-manager-gnome package is indeed a bit misleading
> > > > nowadays.
> > > > Thus for some time I contemplated splitting up the package (similar to how
> > > > Fedora has done) into network-manager-applet and nm-connection-editor. The
> > > > former would contain the nm-applet binary, the latter nm-connection-editor.
> > > > 
> > > > network-manager-gnome would become a transitional metapackage depending on
> > > > both.

This split is now present in unstable.

> In MATE Desktop we actively want / use / rely-on network-manager-gnome. When
> touching the whole thing, may I suggest renaming the bin:pkg
> "network-manager-gnome" to another name? Such es network-manager-applet?

Please see the quoted text above, and please change MATE's dependency to
either nm-applet (if you want the icon in the notification area/"tray")
or nm-connection-editor (if you want the configuration editor) or both
(if you want all of the previous functionality of n-m-gnome).

The network-manager-gnome transitional package cannot usefully be renamed:
the whole point of transitional packages is that they keep the old name,
and depend on the new name(s). But desktop environments can stop depending
on it.

    smcv