technology: return already enabled when tethering is enabled

[framework/connectivity/connman.git] / HACKING

diff --git a/HACKING b/HACKING
index baf7ccd..05fb69c 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -46,7 +46,7 @@ So the normal steps to checkout, build and install such a repository is
 like this:
 
   Checkout repository
-    # git-clone git://git.moblin.org/projects/connman.git
+    # git clone git://git.kernel.org/pub/scm/network/connman/connman.git
     # cd connman
 
   Configure and build
@@ -77,7 +77,12 @@ to use "make install" when testing "connmand". The "bootstrap-configure"
 automatically includes this option.
 
   Run daemon in foreground with debugging
-    # sudo ./src/connmand -n -d
+    # sudo ./src/connmand -n -d 'plugins/*'
+
+The debugging option -d takes an argument. This argument can be a comma
+separated list of file names like 'plugins/wifi.c,plugins/ethernet.c' to
+enable debugs in these files. Simple glob style pattern matching is
+supported in this list.
 
 For production installations or distribution packaging it is important that
 the "--enable-maintainer-mode" option is NOT used.
@@ -97,16 +102,6 @@ Running the daemon with debugging information in the foreground is quite
 verbose and sometimes not really helpful. The "monitor-connman" script
 allows to monitor "PropertyChanged" D-Bus signals from various interfaces.
 
-  During start of daemon
-    {Manager} [/] Devices = dbus.Array([dbus.ObjectPath('/dev_00_90_CC ...
-    {Device} [/dev_00_90_CC_xx_xx_xx] Powered = 1
-    {Device} [/dev_00_90_CC_xx_xx_xx] Networks = dbus.Array( ...
-
-  During shutdown of daemon
-    {Device} [/dev_00_90_CC_xx_xx_xx] Networks = dbus.Array( ...
-    {Device} [/dev_00_90_CC_xx_xx_xx] Powered = 0
-    {Manager} [/] Devices = dbus.Array([], ...
-
 Every "PropertyChanged" signal will generate a line of output. Some of them
 can get very complex. The first detail inside "{ ... }" is the interface
 name (without its service name prefix). The second detail inside "[ ... ]"
@@ -126,7 +121,10 @@ To make the gtk-doc process work, the gtk-doc tools need to be installed.
 Every distribution should provide a package for this, but the naming of the
 package might be different:
 
-  Ubuntu/Debian
+  Debian
+    # apt-get install gtk-doc-tools
+
+  Ubuntu
     # apt-get install gtk-doc-utils
 
   Fedora