On Sunday 21 January 2007 04:23, Joe Morris (NTM) 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. ...
All above is freedom of choice, but foo.rpmnew and foo.rpmsave are result of installation using rpm package manager program. They are way around the problem, not a solution. They exist only if particular package is missing software that will automatically or interactively create configuration file during it's installation. What particular piece of software created them and who directed creation has also little to do with real reason for their existence. I'm sure, if you would be long enough with SUSE, you will notice that number of such files is decreasing with each release and also would come to the same conclusion about the reasons why they are created. BTW, I didn't mentioned who and what created foo.rpmnew and foo.rpmsave, I just noticed that reason is trivial lack of configuration software (script or binary). Why it is missing has also few answers: complexity, lack of interest, lack of time, early development stage or all of that togheater, -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
