On 2008-06-23 Atsuhito Kohda <[EMAIL PROTECTED]> wrote: > On Sat, 21 Jun 2008 19:07:51 +0200, Andreas Metzler wrote: [...] > > afaict conffiles won't work since you build the configuration files in > > postinst using debconf inputs. You'd need to use some clever > > scripting, like ucf.
> I guess if I keep them as configuration files, it needs > only to check if a file exists or not before copying > configuration files and if I changed them as conffiles > I needs to check if they were changed or not with, for example, > md5sums and rmoved unmodified files in preinst (with > version check). ucf might be another option but I don't > understand your point of "conffiles won't work". [...] Hello, Probably just a misunderstanding. I use the term "confile" exclusively for configuration files shipped directly in the .deb, where dpkg itself takes care of not overwriting local customizations. Your configuration file is not shipped in the .deb package but generated at installation time using locally supplied input (default homepage). *Imho* the "default homepage" debconf question is not worth the pain it causes, requiring configuration file managment in maintainer scripts. If it it was my package I would simply drop the debconf thingy and go for dpkg conffiles. ;-) cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
