On Sun, 2017-10-29 at 17:12 +0900, Masashi Honma wrote:
I'm interested in NetworkManager development.
Now I could build NetworkManager and start it by this command.
# Then I stop the existing NetworkManager by service command.
$ ./src/NetworkManager
# I do not run "make install" because I do not want to over write
existing
NetworkManager installed with apt get(I'm on Ubuntu 16.04).
And I think I should build network-manager-applet from this git also.
git://git.gnome.org/network-manager-applet
But before building the network-manager-applet, the existing
network-manager-applet looks boot when I start the NetworkManager
which I built.
Could I use built NetworkManager and network-manager-applet without
over writing
existing them ? If it could, how to use it ?
Regards,
Masashi Honma.
Hi, check https://wiki.gnome.org/Projects/NetworkManager/Hacking You don't need to rebuild the applet, unless you have specific reasons to do so. Either don't use the applet at all (nmcli), or just use the one provided by your installation. Older client versions are compatible with newer server versions, so, the applet provided by your distribution will work, unless you want to work on a server version that is older (which would be odd to do). NetworkManager gets D-Bus activated. So, if you just `systemctl disable NetworkManager` in order to start the version that you built on your own, then it might be restarted again, and conflict. You could for example `systemctl mask NetworkManager`. See `man systemctl`. You can install NM in a separate path, and run it from the terminal with --debug option, so that it doesn't fork to background. You could configure with --prefix=/opt/test \ --localstatedir=/var \ --sysconfdir=/etc \ There is also --run-from-build-dir configure option, so you can run it from the build directory. Good luck, Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part