[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: customized configuration issue (was: Summary of the workshop on CDDs held in Valencia)

On Fri, 14 May 2004, C. Gatzemeier wrote:

> I think the problem is that debconf stores settings as authoritative outside
> of the original config files.
> This was of course done to avoid parsing config files, but it lead to this
> controversy simply since it introduced a separte, potentially conflicting
> config store/registry by design. (That is IMHO of course)
I guess the string "debconf is no registry" will cause many hits
at Google.  If you use debconf "the right way" you parse the config
file first and adjust the debconf database according to changes in the
config files.  So config files have the main priority.  That means in
other words, if you would run cfengine and change some parameters which
are controled by debconf the next run of dpkg-reconfigure <package>
should bring up the values which were set by cfengine as "current".
If not file a bug report against the package in question ...

> The moment settings outside of the original config files are considered as
> authoritative, no matter if by using a "file managed by debconf", cfengine or
> other write-only config file generator approach, either those kind of tools
> conflict and break other tools and manual modifications, or they have to
> refuse working. "File has been modified!" (Who dared to?) "Do you want to
> overwrite it, or discard changes/updates?"
Exactly - but were is the problem here?

Kind regards


Reply to: