I'm trying to develop a linuxconf module for majordomo, which I find to be
a wonderful package but an administrative nightmare. I have both feedback
and questions about Linuxconf.
First, the linuxconf-devel stuff actually seems to work, more or less. I
called setupmod.sh, and it created a development directory. Feeling daring,
I typed 'make' immediately:
emk@kidd:~/src/majordomo $ make
majordomo.cc
In file included from majordomo.cc:11:
majordomo.h:17: majordomo.p: No such file or directory
majordomo.cc:12: majordomo.m: No such file or directory
make: *** [majordomo.o] Error 1
OK, so it won't build yet. A brief examination of userinfo reveals that the
missing files are machine-generated. So, here's a patch which will prevent
future module authors from getting confused:
--- setupmod.sh.old Sun Nov 29 13:03:24 1998
+++ setupmod.sh Sun Nov 29 13:07:03 1998
@@ -180,6 +180,12 @@
echo The summary and description are stored
echo in the files Summary and Description.
echo They will be used to prepare packages.
+echo
+echo Type \'make msg\' to create $module.m
+echo \'make proto\' to create $module.p. To
+echo make the latter command work, you\'ll
+echo need the solucorp-tools package from
+echo ftp://ftp.somewhere.com/pub/solucorp-tools-0.0.tar.gz
And here's the great mystery: where do I get the solucorp-tools package? If
anybody can point me to a copy, I can begin work on majordomo support for
Linuxconf.
Linuxconf, by the way, is an excellent system. Many thanks to Jacques
Gelinas for his excellent work (and RedHat for integrating it with
distribution).
Cheers,
Eric
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
