Greg Morgan wrote:
One of the things I had not designed but thought about was variables. So
here's a possible definition in XML.
XML. That's where I remember this whole idea coming to
a halt a year or so ago, when somebody suggesting using
this and I and a couple of other people said, "yikes."
But still, regardless of that off the cuff response, I really
like your idea of a central database containing
varname = value
pairs that can be sourced. That's what I thought would
be a simple way to create a config-db that's readily available
to hand-editing, shell scripting, and higher level languages.
Please can we keep the db simple? I think Charles concurs
with this in his post. At least he argues for straight text.
o All the configurable files of a package must be collected.
o All the variables in a package must be collected.
You make the case for doing something along the lines
of what I thought of, namely creating .leaf packages
so that their configuration files have been modified to
use the db variables, which are standardized.
Chad Carr makes the case for:
config-db
\
\
interfaced only by an API <------------ api triggered by new packages
\
\
templates of each package config file
\
\
dynamically created run time conf files,
So I think there are two camps evolving in this discussion.
Next you make the final point:
> o All the types of variables used in all LEAF distros must be collected
> and given a type name.
I don't understand why this level of complexity is needed,
unless the XML-php dynamic web page creation thing is where
your idea is headed. As Mike Noyes can tell you, I sort of
anti-php, having been doing webmin stuff back in the days of
Netscape-0.96, before Windows httpds. I like to retain control
of how the page looks, which is slighty anti-the-concept-of-
markup-languages.
> ... Another way to do this would be a configuration file
that is sourced.
I like this idea, because I don't see how environment variables
are bad in this case.
:'a,'b s/^\(.*\)\(=\)\(.*\)$/<Variable Name="\1" Type="simple">^M
<comment><\/comment>^M <value>\3<\/value>^M<\/Variable>/
Ok, you get the sed award of the month. But seriously, would you
please comment on the deficiencies of something like this:
#[weblet]
#:DEPENDENCIES="root etc"
#:DESCRIPTION="A shell based httpd for gathering LEAF statistics"
#:PKGLIST="/etc/weblet.conf /etc/www /www /bin/weblet"
WRN_FW=5
ERR_FW=50
WRN_MEM_PCNT="10"
ERR_MEM_PCNT="5"
WRN_MEM_K="512"
ERR_MEM_K="256"
WRN_DISK_PCNT="10"
ERR_DISK_PCNT="5"
WRN_DISK_K="200"
ERR_DISK_K="100"
WRN_DISK_ram0_K="768"
ERR_DISK_ram0_K="256"
It's sourcable but still contains the glue. Would you
agree that using sourcable straight text config files
is a good system still used by Makefiles?
Best,
Matthew
-------------------------------------------------------
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
