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.
Thoughts?
--Chan
Chan Wilson --- cwilson@sgi.com --- +4138-433-760
Silicon Graphics, SA. Cortaillod, Switzerland.
"Network Analyst" && Irix Guru && Gravitational Engineer
Follow-Ups:
|
|
