HGi all, After re-reading my last postings, I found my own language somewhat sharp. So I must beg your pardon. I can only say that it's the nicotine (or better, lack of it in my blood) who was apeaking. I think I'll get out for some days or at least until I get some valium. Best regards, Roman
HGi all, After re-reading my last postings, I found my own language somewhat sharp. So I must beg your pardon. I can only say that it's the nicotine (or better, lack of it in my blood) who was apeaking. I think I'll get out for some days or at least until I get some valium. Best regards, Roman
So I must beg your pardon. I can only say that it's the nicotine (or better, lack of it in my blood) who was apeaking. I think I'll get out for some days or at least until I get some valium.
Well, I did not realized that :) There is just one problem with configuration files, that we did not solved until now: 1. If installation will overwrite these files - than user will loose it's settings. 2. If it will not overwrite them, plain user will not have ability to set up new things. In any case - make install - under linux should create them at least. But what to do if those files already exist? Should we create some [x]therion.ini.template files? I have no idea. Regards, S.
Stacho Mudrak napsal(a):
So I must beg your pardon. I can only say that it's the nicotine (or better, lack of it in my blood) who was apeaking. I think I'll get out for some days or at least until I get some valium.
Well, I did not realized that :)
There is just one problem with configuration files, that we did not solved until now:
1. If installation will overwrite these files - than user will loose it's settings.
2. If it will not overwrite them, plain user will not have ability to set up new things.
In any case - make install - under linux should create them at least. But what to do if those files already exist? Should we create some [x]therion.ini.template files? I have no idea.
I have one example from Slackware... There is followin setup for startup scripts... If file exists new file with .new suffix is created. L.
+++ Stacho Mudrak [05-03-04 09:39 +0100]:
So I must beg your pardon. I can only say that it's the nicotine (or better, lack of it in my blood) who was apeaking. I think I'll get out for some days or at least until I get some valium.
Well, I did not realized that :)
neither did I - I don't know what you are talking about Roman :-)
There is just one problem with configuration files, that we did not solved until now:
1. If installation will overwrite these files - than user will loose it's settings.
2. If it will not overwrite them, plain user will not have ability to set up new things.
In any case - make install - under linux should create them at least. But what to do if those files already exist? Should we create some [x]therion.ini.template files? I have no idea.
The debian packages solve this by having a concept of 'config' files. These are special files, which if they get overwritten on install (and have been changed since last time), then the installer asks if you want to use the old ones, the new ones, look at the differences etc. For a plain make install, I'm not sure what the normal thing is - I expect just overwriting the old ones is normal. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
Wookey wrote:
The debian packages solve this by having a concept of 'config' files. These are special files, which if they get overwritten on install (and have been changed since last time), then the installer asks if you want to use the old ones, the new ones, look at the differences etc.
rpm does something similar; the installer adds .rpmnew to the new config file and informs the user.
For a plain make install, I'm not sure what the normal thing is - I expect just overwriting the old ones is normal.
Package management systems have an advantage over make install, in that they know whether the old config file has been altered by the user or not. If not they can just update it. Many (most?) source packages don't explicitly copy config files anywhere on make install, but have template versions in the tarball. Users building/upgrading from source can decide what to do. Builders of binary packages can include them using their package managers features. Either way, make install shouldn't be installing files in ~/. If you do install .ini files put them in /etc/. The user running make install may not be the user running the application (in fact will probably be root). John
participants (5)
-
John Pybus -
Ladislav Blazek -
Roman Muñoz -
Stacho Mudrak -
Wookey