On Mon, Nov 01, 2004 at 06:14:57PM +0100, Frank Küster wrote:
> But that could as well be achieved by parsing the configuration files:
That is exactly what packages were the Debconf configuration winds up in
a configuration file have to do. However, Debconf answers will not
always wind up in con
o configuration file exist.
>> >
>> >(This is sometimes summarized using statements like 'debconf is not a
>> >registry'.)
>>
>> Why is the information given during package installation stored
>> persistently in the first place?
>
> As a c
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 sta
sean finney <[EMAIL PROTECTED]> schrieb:
> On Mon, Nov 01, 2004 at 08:04:14AM +0100, Marc Haber wrote:
>> Why is the information given during package installation stored
>> persistently in the first place?
>
> it's not stored persistently, that's why it's in /var/cache :)
But debconf itself think
On Mon, Nov 01, 2004 at 08:04:14AM +0100, Marc Haber wrote:
> Why is the information given during package installation stored
> persistently in the first place?
it's not stored persistently, that's why it's in /var/cache :)
sean
--
signature.asc
Description: Digital signature
t
>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'.)
Why is the information given during package
6 matches
Mail list logo
