Re: Configuration by using local packages
> * W. Borgert <email@example.com> [040425 16:29]:
> > 3. Create local (empty) package overwriting existing config files
> > by using cp in postinst.
> > => relatively BAD - If new important sections or keywords appear
> > in the config files, they are just over-written.
> Well, isn't that the point of having your own config files around?
> If dpkg updates a package in a way it would have a new config file,
> it will just warn you as if you changed the file manually. Thus
> you can see if you want to change the config you ship. (If there
> is anything bad at it, then that one will get this questions on every
> host one upgrades).
Maybe I didn't make my point clear: If I create a local
(empty) package, that overwrites existing config files - of
other packages! - by using cp in - it's own - postinst, this
will just overwrite the config files, no matter what version
they are etc. My conclusion: "relatively BAD".
W. Borgert <firstname.lastname@example.org>, http://people.debian.org/~debacle/