Retain upgrade paths (was: /etc/redhat-release?)

Peter Bowen pzb at datastacks.com
Thu Sep 25 09:10:20 UTC 2003


On Thu, 2003-09-25 at 02:01, Axel Thimm wrote:
> On Wed, Sep 24, 2003 at 06:58:58PM -0400, Bill Nottingham wrote:
> > Such a script can be *easily* modifed to work with Fedora Core
> > in this case. It can key off of:
> > 
> > a) 'Fedora Core' in /etc/redhat-release
> > b) the presence of /etc/fedora-release
> > c) the fact that fedora-release provides /etc/redhat-release
> > 
> > Note that b) and c) will only be true in test release 3 and later.
> 
> You are missing the point, the "script" is rpm/apt/yum/<your favourite
> package resolver here>
> 
> Here is what is current practice for the upgraders (as opposed to
> "freshinstallers"):
> o Install RH8.0
> o Install apt/yum
> o Use repo A, B and C (pointing to its RH8.0 section)
> o User decides to upgrade to RH9
> o Upgrade the system with RH9 CDs
> o Adjust the apt/yum configuration to the new version
> o Update the system against the repos for RH9
> 
> There is no space for a custom script, unless you are thinking of
> anaconda specials, which is not desired.

There is a space for custom scripts, in the spec generation process.  It
is clear that you already have some custom script to help automate
building packages for all the different distro versions.  Just modify
the script to look for one of the things that Bill mentioned, and either
internally add 9 to the version or do something else to cause rpmvercmp
to sort your EVR before the older EVR.  No one is suggesting that
rpm/yum/up2date/anaconda/apt/red-carpet should be modified in any way.

Thanks.
Peter





More information about the fedora-devel-list mailing list