On Fri, 5 May 2006 at 19:39:26, Dan Williams wrote: > But in any case, there are no _runtime_ dependencies on Gnome of any > sort in the core daemon, and if there were, we'll take them out.
Thanks for your reply, so it is possible to build it (version 0.6.2) with GNOME support and then manually separate GNOME independent things (daemon) and GNOME specific things (panel applet, etc.) to different packages? I am asking because of packaging NetworkManager for Arch Linux. > Note that to get any use out of NM you'll need to have an info-daemon > for your situation, if you're not running Gnome or KDE. That > info-daemon just sends configuration bits to NM from your specific > distro and/or desktop environment. If you don't have an info-daemon, > you'll likely not be able to connect to wireless networks that are > encrypted, simply because there's nowhere to store that information. Well, my original motivation for trying NetworkManager was only detection of network cable connect/disconnect events. I had written to hal mailing-list why there aren't some LinkUp/LinkDown HAL signals if network cable is connected / disconnected (I want to catch these signals with ivman and run for example /etc/rc.d/network stop/start or some other programs). But Kay Sievers told me that this feature has moved from HAL to NetworkManager and I should use NetworkManager for it. So here I am :-) Is something like that possible only with NetworkManager daemon? Do NetworkManager send some DBUS signals when network cable is connected and disconnected? Michal Krenek (Mikos) _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
