Lynn Avants wrote:
Again, I agree tweaking the existing package configuration process to simplify configuration is a good trade-off. When it comes down to it, most of the existing varients of LEAF already have a pretty "customized" configuration process (ie a typical RedHat, Suse, or even Debian user wouldn't initially feel right at home). I also like the idea of using a database type application to assist both the packaging system and package management.This is exactly what I have had in mind..... I'm still working on the database/variable file for my own testing. The only problem with this idea is that it modifies existing packages (substution variables), but it nullifies the need to generate all the needed conf files saving tons of space and re-packaging as well. I feel this is an acceptable change and have personnally had a set of install scripts for Dachstein that take the other 'regenerate-method' posted from my /devel directory for over a year now. These methods will work with *any* front-end and eliminate a lot of common errors that are made via hand-editting.
To avoid re-inventing the wheel, I would suggest an RDB format database system, which is built out of plain ascii text files, and manipulated with small programs via shell scripts. Something like rdb (perl) or nosql (shell & awk):
ftp://ftp.rand.org/pub/RDB-hobbs/
http://www.linux.it/~carlos/nosql/
It has always been my intention to use something like this (ported to pure shell, or perhpas with a few complex modules written in c or forth) for the next generation packaging system, so using it for configuration too would be a good thing. :)
--
Charles Steinkuehler
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
