Drop nm-connection-editor?

drago01 drago01 at gmail.com
Thu Feb 13 20:02:31 UTC 2014


On Thu, Feb 13, 2014 at 9:01 PM, Adam Williamson <awilliam at redhat.com> wrote:
> On Thu, 2014-02-13 at 14:48 -0500, Bastien Nocera wrote:
>>
>> ----- Original Message -----
>> > On Sat, 2014-02-08 at 20:04 +0200, Elad Alfassa wrote:
>> > > We can't drop it: There are things it does the Network panel can't do. The
>> > > Network panel actually invokes nm-connection-editor in many cases.
>> > >
>> > > Anyway, I do think we should either split the .desktop file to a separate
>> > > subpackage that won't be installed by default, or add a rule in the
>> > > .desktop file saying it shouldn't be shown in GNOME.
>> >
>> > nm-ce is intended to be the "everything" option; it's very
>> > understandable that the GNOME network panel won't necessarily implement
>> > everything that NM can do (for example, Data Center Bridging), so we may
>> > wish to keep it available.  That doesn't mean it has to be installed by
>> > default though.
>> >
>> > The panel still uses the editor for 802.1x setup and some advanced stuff
>> > I think.  I'm fine with setting "don't show in GNOME", but that would
>> > ideally be either (a) a Fedora specific patch, or (b) if there was some
>> > way to restrict it to GNOME 3.6+ but leave it for GNOME 2.x.
>>
>> In Fedora 20 at least, nm-connection-editor is only to:
>> - edit information about Wi-Fi devices, but we can't actually get to it
>>   from anywhere in the UI
>> - Launching an editor for unknown connection types
>>
>> I think we could probably remove the dependency altogether...
>
> Now I'm thinking about this, IIRC anaconda depends on it, so even if you
> remove the dep from GNOME itself, live installs will still have it
> present after installation. You can remove anaconda post-install, but
> most people don't.

It probably should remove itself and other stuff like
"livesys.service" after install.


More information about the desktop mailing list