[ Chan Wilson writes: ]
>
> The current scheme of returning the list configuration file is simply
> a direct dump of whatever happens to be in <listname>.config.
> Usually, this isn't a problem, but when adding or replacing list
> variables, a problem arises: The new variables won't be seen, and
> obsoleted variables will get bounced back as unknown by newconfig.
>
> What I'm proposing to do is have the list config file be a pure list of
>
> variable = value
>
> with *no* commentary. When the 'config' command returns the list
> configuration, it will return a "commented" version with any new
> variables added and old variables removed. 'newconfig' will then
> simply be a dump of the $config_opts{$list} hash.
And what happens to any comments I might insert? Eaten by the
"de-commenter", no doubt. The easiest thing to do is to supply a
conversion program to run on existing installations to update the config
files. That reduces the changes and complexity required in Majordomo for
something that only needs to be done once for all lists.
JMO, but it seems to me that incompatible changes such as this are
inappropriate for a minor revision, i.e. 1.93 --> 1.94, and should be
reserved for major revisions, i.e. 1.93 --> 2.0.0 (yes, I think the
current Mj revision numbering is broken too).
--
Dave Wolfe *Not a spokesman for Motorola*
Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598
Follow-Ups:
References:
|
|
