[Pkg-utopia-maintainers] Bug#743138: Bug#743138: [Needs upstream 0.9.10 release] Please only enable ifupdown plugin when ifupdown installed

[Andrej Shadura]

On Mon, 31 Mar 2014 14:02:24 -0700 josh at joshtriplett.org wrote:
> On Mon, Mar 31, 2014 at 08:49:57PM +0200, Michael Biebl wrote:
> > Am 31.03.2014 20:40, schrieb Josh Triplett:
> > > On Mon, Mar 31, 2014 at 04:36:47PM +0200, Michael Biebl wrote:
> > >> Am 30.03.2014 23:00, schrieb Josh Triplett:
> > >>> NetworkManager 0.9.10 upstream will add support for a .d configuration
> > >>> directory, and syntax to incrementally enable plugins
> > >>> (plugins+=pluginname).  This would allow a package like ifupdown to ship
> > >>> a configuration file enabling and configuring the ifupdown plugin, which
> > >>> could then otherwise remain disabled.
> > >>
> > >> This is certainly an interesting idea, but there a few issues:
> > >> a/ the ifupdown plugin not only parses /etc/network/interface but e.g.
> > >> also provides the hostname information stored in /etc/hostname, which we
> > >> want even if ifupdown is not installed.
> > > 
> > > That shouldn't be in the ifupdown plugin; NetworkManager should ideally
> > > be unconditionally getting it from /etc/hostname or from hostnamed.
> > 
> > Getting it unconditionally is a bit problematic, since on most
> > distributions /etc/hostname didn't exist. Now that systemd chose to use
> > /etc/hostname, the situation is a bit different.
> > 
> > Care to forward that to upstream?
> 
> Done: https://bugzilla.gnome.org/show_bug.cgi?id=727407

Quoting the upstream:

> this is fixed a while ago.
> 
> Handling of hostname moved from the settings plugin to NMSettings.
> Also, hostnamed is supported as one of several options.
> 
> There were many changes there, so I am not going to hunt down for a particular BZ which fixed this. However, the functionality is now all in https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/nm-settings.c


-- 
Cheers,
  Andrej