On Sunday, January 21, 2007 @ 4:24 AM, Joe Morris wrote: >Rajko M. wrote: >> On Saturday 20 January 2007 18:39, Joe Morris (NTM) wrote: >> >> >>> Along with many others. It is just a part of the process of learning >>> your new system, one that is robust enough to tell you things you should >>> do, but not so overbearing as to force its own changes on you, i.e. >>> freedom. >>> >> >> Joe, >> >> in this case freedom has little to do with fact
>Sure it does, you can choose to use another packager, do it yourself, >install from source, etc., as opposed to say Windows, which will decide >all those things for you without asking or usually telling you, the >computer owner. Isn't it really a matter of Windows not automatically installing third-party upgrades? There really is no package manager analogy for Windows, right? Any third party software you install/upgrade on Windows you do it interactively, so if there are any questions that need to be asked they can be asked right at that point. With RPMs, there is no interaction, so the package manager pretty much has to do things the way it does. >> that some postinstall script >> can't change your configuration file automatically as it is not designed to >> cover all possible variations, and it is missing interactive part that will >> ask you what to do. Makes perfect sense. >rpmnew files are not created by postinstall scripts. They are created >by telling rpm via the spec file that a particular file is a config >file, and whether to replace the old config file (creating a rpmsave >file) or by not replacing it, creating the rpmnew [via >%config(noreplace) in the files section]. This is done by rpm, not a >script AFAIK. It is controlled by the package maker via the spec file. I think you're both saying the same thing here. >> It is just a way to skip creation of bloated postinstall >> scripts, or change your working configuration with some default settings, >> forcing you to go trough configuration again. >I believe the package maker should know if the old config file would no >longer work or not. Since they control that fact, our choice is to >trust the packager to stay true to the package programmers and install, >or not install, and do it another way. Both of the above seem to be true. <snip> >-- >Joe Morris >Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
