On Wednesday 17 March 2010 15:38, Kim B. Heino wrote: > This patch changes how dpkg handles config files. There are three modes: > > 1) If config file is unchanged by user then it will be overwritten. If > changed, then new config file will be created as configfile.dpkg-new. > This is how "real dpkg" handles config files. > > This is the default mode. "Real dpkg" parameter: --force-confdef > > 2) Parameter -N. Always overwrite config files. > > "Real dpkg" parameter: --force-confnew > > 3) Parameter -O. Never overwrite, always create .dpkg-new. > > "Real dpkg" parameter: --force-confold > > > This is version 3 of this patch. Changes: > > - "Changed by user?" -check added. > - -N and -O options added. > - Not a config option anymore (because of default mode).
Great! Please add long options instead of adding non-compatible short ones. http://unixhelp.ed.ac.uk/CGI/man-cgi?dpkg says that -O exists and is aliased to --selected-only. > Comments needed: > > Currently BusyBox-dpkg overwrites config files (new option -N). This > patch changes default action to match "real dpkg". Is this change > allowed? Yes. In the long run, pain from having noncompatible behavior is worse than pain from one-time conversion for the users which depend on current behavior. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
