I totally agree that it is a pain that you can't set the force install a new version of a conffile. As a workaround, an uninstall then install can help. This way, the conffile is deleted (I don't think there is a "purge" as with dpkg).
Ben ________________________________________ De : [email protected] [[email protected]] de la part de Michael Olbrich [[email protected]] Date d'envoi : mercredi 2 mars 2011 12:28 À : [email protected] Objet : Re: [ptxdist] Configuration files management On Tue, Mar 01, 2011 at 02:02:48PM +0100, Benoît Burnichon wrote: > For the conffile thing in the pkg control directory, I think the best is > effectively to follow the same architecture than install_alternative > (install_conf_alternative for the name?). install_config I think. With the search dirs from install_alternative. > When an ipkg get installed or updated, the preinst script should be called > differently. > Case of a fresh installation: preinst install version > Case of an upgrade: preinst upgrade oldversion > > http://buffalo.nas-central.org/wiki/Construct_ipkg_packages_(for_developers)#Things_common_to_all_CONTROL_Scripts > > The installation scripts could find the CONTROL directory and conffiles file. > > In case the configuration file has changed, it will ask for the user to make > a decision (as dpkg does): keep the old, take the new, show diff With the > -force-defaults option to ipkg, the old conf is kept without asking. I really don't like it, that there is no way to force the new config file. For me the typical use case is, that the config file is unmodified and a new version of the package contains a new version of the config file. Regards, Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list [email protected] -- ptxdist mailing list [email protected]
