Hi Sylvain,
ps : should if fullfill the requirement of your policy line not to write configuration file, except when people changes things in debconf ?
I think so. that is, don't overwrite the file in the postinst, just in
the dpkg-reconfigure process.
Hello,[...]
On Thu, Aug 19, 2004 at 04:17:47PM +0200, Adeodato Sim� wrote:
Hi Sylvain,
ps : should if fullfill the requirement of your policy line not to write configuration file, except when people changes things in debconf ?
I think so. that is, don't overwrite the file in the postinst, just in
the dpkg-reconfigure process.
Ok, i have turned it 20 times in my head to find a reasonnable solution
for your problem.
Here is my proposal :
On Thu, Aug 19, 2004 at 11:00:37PM +0200, Sylvain LE GALL wrote:
Hello,
On Thu, Aug 19, 2004 at 04:17:47PM +0200, Adeodato Sim� wrote:
Hi Sylvain,
ps : should if fullfill the requirement of your policy line not to write
configuration file, except when people changes things in debconf ?
I think so. that is, don't overwrite the file in the postinst, just in
the dpkg-reconfigure process.
Ok, i have turned it 20 times in my head to find a reasonnable solution
for your problem.
Here is my proposal :[...]
Hmm, many packages do actually solve this by parsing the config file on upgrade and using the old values as default to the debconf questions. Wouldn't this be possible here, too (The format doesn't seem too complicated)?
* Frank Lichtenheld [Thu, 19 Aug 2004 23:39:53 +0200]:
On Thu, Aug 19, 2004 at 11:00:37PM +0200, Sylvain LE GALL wrote:
Hello,
On Thu, Aug 19, 2004 at 04:17:47PM +0200, Adeodato Sim� wrote:
Hi Sylvain,
ps : should if fullfill the requirement of your policy line not to write
configuration file, except when people changes things in debconf ?
I think so. that is, don't overwrite the file in the postinst, just in
the dpkg-reconfigure process.
Ok, i have turned it 20 times in my head to find a reasonnable solution for your problem.
Here is my proposal :[...]
Hmm, many packages do actually solve this by parsing the config file on upgrade and using the old values as default to the debconf questions. Wouldn't this be possible here, too (The format doesn't seem too complicated)?
it's one possibility.
FYI, there was a similar bug recently reported against gpm (#266822),
which the maintainers resolved by switching to ucf. you may wish to
investigate that too.
thanks,
Ok, another user propose me a patch just to read the conffiles if it
exists and try to update the debconf values.
I will use a temporary file as suggested in ucf examples and use ucf to
keep things well with absolute requirement of the policy...
What do you think of this ?
On Thu, Aug 19, 2004 at 11:00:37PM +0200, Sylvain LE GALL wrote:
Hello,
On Thu, Aug 19, 2004 at 04:17:47PM +0200, Adeodato Sim� wrote:
Hi Sylvain,
ps : should if fullfill the requirement of your policy line not to write
configuration file, except when people changes things in debconf ?
I think so. that is, don't overwrite the file in the postinst, just in
the dpkg-reconfigure process.
Ok, i have turned it 20 times in my head to find a reasonnable solution
for your problem.
Here is my proposal :[...]
Hmm, many packages do actually solve this by parsing the config file on upgrade and using the old values as default to the debconf questions. Wouldn't this be possible here, too (The format doesn't seem too complicated)?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 45:09:41 |
| Calls: | 12,111 |
| Calls today: | 2 |
| Files: | 15,010 |
| Messages: | 6,518,466 |