readme: update with a bit more information

- accept patches to the infrastructure
- document known limitations

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

diff --git a/README b/README
index a02ff2c0032fa317916924ce809ada860c84b268..408a67b90dabb0707bd96982aae33c58e790c1ef 100644 (file)
--- a/README
+++ b/README
@@ -10,3 +10,33 @@ Such changes shall be directed directly to the appropriate mailing
 list, and they will eventually find their way is this package at
 the next sync:
     mailto:linux-kbuild@vger.kernel.org
+
+However, if there is a bug in the packaging infrastructure, patches
+are most welcome, of course! Most notably, because this is my very
+first autostuff-based package, I may have done mistakes here and
+there...
+
+As such, there are currently a few known limitations:
+
+- statically linking is much, much more complex than it should be.
+  I have been seemingly able to build part of the frontends with
+  such incantations of ./configure and make:
+    ./configure LDFLAGS=-static --disable-shared --enable-static    \
+                --disable-gconf --disable-qconf
+    make LDFLAGS="-all-static -static-libtool-libs" nconf_EXTRA_LIBS=-lgpm
+
+- the nconf frontends requires (at least on my machine) to linked
+  against GPM; this is not detected when staticaly linking (hence
+  the nconf_EXTRA_LIBS in the command above).
+
+- statically linking the graphical frontends (gconf and qconf) is
+  *not* supported: I am missing static libs for Qt3Support, so
+  qconf does not link. And there is a stupid bug in libtool that
+  prevent properly linking against installed static libraries
+  (seemingly fixed in 2.4, but not quite yet, in fact...), so
+  gconf does not link. That's why they are disabled above.
+
+Note that, provided you have the required dependencies, all
+frontends are properly built if you link dynamicaly. The following
+just works as expected:
+    ./configure && make