Re: Build NetworkManager without GNOME dependencies
- From: Dan Williams <dcbw redhat com>
- To: Michal Krenek <mikos sg1 cz>
- Cc: networkmanager-list gnome org
- Subject: Re: Build NetworkManager without GNOME dependencies
- Date: Fri, 05 May 2006 13:37:42 -0400
On Fri, 2006-05-05 at 19:11 +0200, Michal Krenek wrote:
> Hello,
> is it possible to build NetworkManager without GNOME support? I don't want
> GNOME dependencies in my system only for NetworkManager. On
> http://www.gnome.org/projects/NetworkManager there is this paragraph:
>
> "The most important pieces of NetworkManager are desktop-environment and
> distribution agnostic, functioning just as well in Gnome, KDE, Xfce, etc.
> across distributions like Fedora Core, Ubuntu, SuSE, Debian, and Gentoo."
>
> It's nice, but if I try ./configure --help, there aren't any options to
> disable GNOME support :-(
>
> Is there some way how to build it without GNOME dependencies? This software
> really shouldn't depend on some desktop environment, it should be
> desktop-independent like for example hal.
The core NetworkManager daemon doesn't depend on anything Gnome
specific. It basically requires hal, glib, and dbus. glib != gnome
too.
Right now, the Gnome bits (namely, everything in the gnome/ directory in
CVS) _do_ require gnome, and the autogen.sh script requires the
gnome-common module. The dep on gnome-common should probably go away,
but that's only a build-time dep and definitely not a runtime one.
We also likely need a configure time option to disable the Gnome applet,
and to disable the configure-time checks for gnome-y bits in
configure.in.
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.
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.
Dan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]