Ben Reser wrote:
In this situation either way you go you'll run into issues. If youNo, the best intermediate situation is to diff the current config to the default config and then patch the result into the new config. If it isn't possible warn the user. If it is too dangerous, make it configurable, but anyway after the upgrade advise the user which config files have to be checked (always reminding him the changes he made to the original config file).
replace config files, you'll have unhappy people complaining that their
configs were ovewritten and that they would have worken just fine. If
you don't then you'll have people with issues because of their configs.
What has been done is the best intermediate situation that can. Configs
get upgraded so long as the config file that was installed by the
current RPM has not been changed.
The problem doesn't end with config files, though, there are also changes in data files (e.g. db3, db4...) and user config files.
Anyway, how does debian handle this mess? (I'm asking because debian users usually brag about how they only need to install once)
Bye
--
Luca Olivetti
Note.- This message reached you today, it may not tomorrow if you
are using MAPS or other RBL. They arbitrarily IP addresses not
related in any way to spam, disrupting Internet connectivity.
See http://slashdot.org/article.pl?sid=01/05/21/1944247 and
http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad.html
msg85624/pgp00000.pgp
Description: PGP signature
