[Pkg-utopia-maintainers] Bug#497108: Bug#497108: /usr/bin/nm-vpn-properties belongs to the network-manager-gnome package

Vincent Caron vincent at zerodeux.net
Mon Sep 1 10:54:51 UTC 2008


On Mon, 2008-09-01 at 12:22 +0200, Michael Biebl wrote:
>
> No, you are right, the network-manager package has no GNOME dependencies
> although it ships nm-vpn-properties, a GNOME application.
> 
> This is actually a bit of a hack.
> The monolithic NetworkManager source tarball was split into a core part
> and GUI/GNOME part in version 0.6.5. Unfortunately nm-vpn-properties
> remained in the core network-manager package.
> We had the option to split nm-vpn-properties into yet another package,
> make the network-manager binary package depend on GNOME libs, or cheat a
> little and exclude the GNOME dependencies from network-manager.
> We chose the last option. We assumed, that anyone using
> nm-vpn-properties will also use nm-applet from network-manager-gnome,
> which will pull in all the necessary dependencies.
> Another reason was, that in the upcoming 0.7 release, nm-vpn-properties
> will be dropped from the network-manager core package, so a separate
> binary package seemed like a bit of overkill.
> And making the network-manager binary depend on GNOME libs was also not
> an option, given that it is used by KDE only desktops.
> 
> Hope this clarifies the situation a bit.

  Absolutely, thanks for the insight. It's effectively okay for me in
the end since aptitude installed the 'network-manager-gnome' alongside
(because it's a Recommends).

  It turned out that I was investigating a bug (all my gnome app
starting in 'offline mode', fixed) and exploring the network-manager
binaries in a X-less root shell: nm-vpn-properties unexpectedly asked
for a display. I thought I would notify.

  Case closed it seems :).







More information about the Pkg-utopia-maintainers mailing list