[lvm-devel] [PATCH 01/15] configure.in: improve --with-clvmd description

[Fabio M. Di Nitto]

It is possible to build all clvmd locking backends at once
but it doesn't really make sense in real life.

Improve the text to describe the most common scenarios.

Signed-off-by: Fabio M. Di Nitto <fdinitto at redhat.com>
---
:100644 100644 18bac05... f9e5d8d... M	configure.in
 configure.in |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/configure.in b/configure.in
index 18bac05..f9e5d8d 100644
--- a/configure.in
+++ b/configure.in
@@ -325,7 +325,12 @@ AC_MSG_RESULT($REALTIME)
 dnl -- Build cluster LVM daemon
 AC_MSG_CHECKING(whether to build cluster LVM daemon)
 AC_ARG_WITH(clvmd,
-  [  --with-clvmd=TYPE       Build cluster LVM Daemon: cman/gulm/corosync/none/all
+  [  --with-clvmd=TYPE       Build cluster LVM Daemon.
+                          The following locking combinations are valid:
+                           * cman,gulm             (RHEL4 or equivalent)
+                           * cman                  (RHEL5 or equivalent)
+                           * cman,corosync,openais (or selection of them)
+                           * none                  (disable build)
                           [TYPE=none] ],
   [ CLVMD="$withval" ],
   [ CLVMD="none" ])
-- 
1.5.4.3