After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 663523 - Gnome-shell requires networkmanager as a necessary dependency.
Gnome-shell requires networkmanager as a necessary dependency.
Status: RESOLVED WONTFIX
Product: gnome-shell
Classification: Core
Component: building
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-06 19:15 UTC by Manjul Apratim
Modified: 2012-01-12 18:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Manjul Apratim 2011-11-06 19:15:56 UTC
While updating my Arch install, I noticed that gnome-shell, gnome-control-center, and empathy have networkmanager listed as a necessary dependency. This also seems to be the case from the git tree:

http://git.gnome.org/browse/gnome-shell/tree/configure.ac?h=gnome-3-2#n83

Whilst networkmanager is a perfectly excellent tool for managing networks, I have been using wicd for quite some time, from the days when networkmanager needed a GUI to function (I am not sure if it still does), and would try to avoid having two network configuration tools installed if I can. Aside from the fact that networkmanager is officially a part of gnome and integrates well, is there another technical reason that the above applications require network-manager as a necessary and not optional dependency? If not, is it possible for it to be marked an optional dependency?
Comment 1 Milan Bouchet-Valat 2011-11-06 19:29:15 UTC
(In reply to comment #0)
> Whilst networkmanager is a perfectly excellent tool for managing networks, I
> have been using wicd for quite some time, from the days when networkmanager
> needed a GUI to function (I am not sure if it still does)
It doesn't now, see nm-cli.

> , and would try to
> avoid having two network configuration tools installed if I can. Aside from the
> fact that networkmanager is officially a part of gnome and integrates well, is
> there another technical reason that the above applications require
> network-manager as a necessary and not optional dependency? If not, is it
> possible for it to be marked an optional dependency?
I don't think so. Making NM optional would mean adding checks in too many places, which adds more work, clutters the code and creates hard to test configurations. And to benefit to how many people? Do you think people would really build gnome-shell from source just to disable NM support?

The idea is that there's no point in supporting several network configuration systems. NM is the way to go, it allows for a good integration with the desktop. Promoting it in GNOME is also a way to incite people to report bugs there and improve it, which ensures all the network stack works how it should.

If you have reasons to use Wicd rather than NM, you should file bugs. If you haven't, well, it's time to switch... ;-)
Comment 2 Manjul Apratim 2011-11-08 21:55:26 UTC
Thank you very very much! I don't think I am switching back to nm anytime soon (for now), but I am perfectly content with this point of view!