[PATCH] clean up the logging patch a bit to make the option more like the other options.

Also documented it and added it to the .spec file.

1 files changed, 16 insertions, 6 deletions

diff --git a/README b/README
index 123fce6a..26032c35 100644
--- a/README
+++ b/README
@@ -30,18 +30,28 @@ To use:
   Note:
       There are a number of different flags that you can use when building
       udev.  They are as follows:
-	prefix - set this to the default root that you want udev to be
+	prefix
+		set this to the default root that you want udev to be
 		installed into.  This works just like the 'configure --prefix'
 		script does.  Default value is ''.  Only override this if you
 		really know what you are doing.
-	USE_KLIBC - if set to 'true', udev is built and linked against the included
-		version of klibc.  Default value is 'false'.
-	DEBUG - if set to 'true', debugging messages will be sent to the syslog
-		as udev is run.  Default value is 'false'.
-	USE_DBUS -  if set to 'true', DBUS messages will be sent everytime udev
+	USE_KLIBC
+		if set to 'true', udev is built and linked against the
+		included version of klibc.  Default value is 'false'.
+	USE_LOG
+		if set to 'true', udev will emit messages to the syslog when
+		it creates or removes device nodes.  This is helpful to see
+		what udev is doing.  This is enabled by default.  Note, if you
+		are building udev against klibc it is recommended that you
+		disable this option (due to klibc's syslog implementation.)
+	USE_DBUS
+		if set to 'true', DBUS messages will be sent everytime udev
 		creates or removes a device node.  This requires that DBUS
 		development headers and libraries be present on your system to
 		build properly.  Default value is 'false'.
+	DEBUG
+		if set to 'true', debugging messages will be sent to the syslog
+		as udev is run.  Default value is 'false'.
 
       So, if you want to build udev using klibc with debugging messages, you
       would do: