On Fri, 04 Mar 2005 09:39:56 +0100 Stacho Mudrak <s.m@speleo.sk> wrote:
1. If installation will overwrite these files - than user will loose it's settings.
I think we could check for the files. If they exist in rigth places, we could assume they are good, so install script a) does nothing b) rename them to .bkp (or .new, as suggested by Ladislav) -no settings are loosed. BTW, why the files can be on so many directories? I think they should be under /etc on *nix and under Program files\therion on windows. It would be simpler. May be Wookey, as debian developer, knows it better. I found some debian packages who ask when detected user-edited configuration files, (but at this moment I can't remember which ones) If this is a matter of shell scripting, I could work on it.
2. If it will not overwrite them, plain user will not have ability to set up new things.
I'm missing something here. What things couldn't be edited? Or, do you mean that install will ask things to set good values? Regards, Roman
Roman Muńoz napsal(a):
On Fri, 04 Mar 2005 09:39:56 +0100 Stacho Mudrak <s.m@speleo.sk> wrote:
1. If installation will overwrite these files - than user will loose it's settings.
I think we could check for the files. If they exist in rigth places, we could assume they are good, so install script a) does nothing b) rename them to .bkp (or .new, as suggested by Ladislav) -no settings are loosed.
BTW, why the files can be on so many directories? I think they should be under /etc on *nix and under Program files\therion on windows. It would be simpler.
This is *nix standard. You can have global configuration in /etc but each user can change settings for own session in ~/.therion directory L.
I'm missing something here. What things couldn't be edited? Or, do you mean that install will ask things to set good values?
If I add new setting to xtherion.ini file, if it will not be rewritten, user will not see, that this setting is possible. OK - I think that creating .new files would be OK. Another point - many programs read settings from several places. /etc is a problem for non-root *nix users. S.
Sorry to come in a bit late... On Fri, Mar 04, 2005 at 12:35:08PM +0100, Stacho Mudrak wrote:
If I add new setting to xtherion.ini file, if it will not be rewritten, user will not see, that this setting is possible.
So you're talking about the case when a new option is added and the default setting is added to the shipped configuration file? It's particularly annoying to have your carefully tuned configuration swept aside by an upgrade when the only reason is to add a few "do nothing" lines to the default file. This is one think I dislike about RPMs - the attitude that it's OK to nuke my configuration files because you saved a backup is just unhelpful. I want my system to still work after an upgrade, not to have to remember to go back and fix up heaps of configuration files. Debian at least asks you up front what you want to do if the shipped configuration has changed and you modified it locally. Not perfect, but a lot more helpful. I'd much rather regard the shipped xtherion.ini as documentation to consult. Or alternatively write a simple "xtherion.ini updater" which checks which options are unused in the current xtherion.ini and adds them with default settings. Save a backup of the old one in case the update goes wrong - *that* is what backups are for. Cheers, Olly
participants (4)
-
Ladislav Blazek -
Olly Betts -
Roman Muñoz -
Stacho Mudrak