SLUG Mailing List Archives
Re: [SLUG] apt-rpm looks great (was: [Re: Which XFree86 is Applicab le for RedHat 7.1 ?])
- To: lukekendall@xxxxxxxxxxxxxxxx
- Subject: Re: [SLUG] apt-rpm looks great (was: [Re: Which XFree86 is Applicab le for RedHat 7.1 ?])
- From: Mike MacCana <mikem@xxxxxxxxxxxx>
- Date: Sun Mar 9 10:11:08 2003
- Cc: Sydney Linux Users Group <slug@xxxxxxxxxxx>
On Sat, 8 Mar 2003 lukekendall@xxxxxxxxxxxxxxxx wrote:
> On 7 Mar, Mike MacCana wrote:
> > Its possible, people have done it before.
> > But personally I'd rather just do an upgrade, and I don't see what there
> > is to `fix'. An hour or two scheduled maintenance once a year isn't a
> > big deal for me. Remember, Red Hat aim to keep binary compatibility
> > within major version numbers, so 7.x - 7.(x+1) is, in my brain,
> > equivalent to a service pack in the windows world. And, or course, what
> > you're upgrading to is stable with much testing, fixing and (these days)
> > three beta releases before its declared so.
> rpm doesn't merge your changes to config files, though, or help you do
> it interactively.
It will preserve your existing configs, unless the format for the config
file has changed, in which case it will move your old config gile to a
backup name. See install.log for any instances of the latter happening.
* For most packages these days, the config file rarely if ever changes.
They may get more options, but the old configs are still valid.
* The only one (that I use) I can think of recently was Apache 1.x - 2.x.
IIRC, Red Hat may have provided a migration tool.
> The only way I know to do it is to note down each
> ..rpmnew file, and carefully run sdiffs or edit the old and new manually.
.rpmnews are irrelevant. .rpmsaves are where you need to do some work. But
you don't need to note each of them, look in install.log
> Doing it for a whole system is a daunting task.
I find it not so - again, very few packages 9that I use, though I
use a lot change their config file format between versions.
> At work, when we release new versions of products, we either maintain
> backward compatibility, or provide update tools for the old data files.