[ Please don't Cc: me when replying to my message on a mailing list. ] Guy Maor: > This is needed so that the frontend Your sentence not finished. > 4. cfgtool currently stores variables as 3-tuples (variablename, > value, helpfile). Let's make that of arbitrary length by allowing > variables to have attributes, and cfgtool stores the value for each > attribute. Value is just then another attribute, as are helpfile, > onelinedescription, type, etc. This can be done in 2 ways in cfgtool > itself - it has a preset list of attributes somewhere or they can be > made arbitrary. Both are pretty trivial to implement. This sounds good. I'll see if I can implement it soon. First attempt at design: each attribute is given a name; the value is "value", help text in English is "help.en", and so on cfgtool gets new options: --get-attribute <variable> <attribute> --set-attribute <variable> <attribute> <value-of-attribute> the existing options --[gs]et become synonyms for --[gs]et-attribute: --get <variable> --get-attribute <variable> value --set <variable> <value> --set-attribute <variable> value <value> similar changes to the C library interface I'm not sure how the change affects the way the variable database is stored, but that's a minor detail, since no-one is using cfgtool yet. (Except for me, just to keep me on the edge. I changed my /etc/init.d/boot to use cfgtool.) -- Please read <http://www.iki.fi/liw/mail-to-lasu.html> before mailing me. Please don't Cc: me when replying to my message on a mailing list.
Attachment:
pgp0u9_ax3tWU.pgp
Description: PGP signature