| Petter Reinholdtsen 2004-10-30, 8:46 pm |
| [Jesus Climent]
> The problem being that X using Debconf to store information, Y
> modifying the info and then X getting an upgrade, the info stored by
> X using Debconf might be used again to set the values in the data
> file, which will break the initial purpose of Y.
Well, the solution to this problem is to _never_ use debconf to store
information. The configuration info should be stored in the
configuration files, and the current debconf values should be set
based on the content of the configuration files. The values in the
debconf database should only be used when no configuration file exist.
(This is sometimes summarized using statements like 'debconf is not a
registry'.)
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|