On Tue, Jun 22, 2004, F. Even wrote:

Frank!

> > On Mon, Jun 21, 2004, F. Even wrote:
> > 
> > > [...] seem then that the 1.9 bootstrap would need an upgrade....
> > > 
> > I created the upgrade companion packages and added them to the
> > ftp download area ftp://ftp.openpkg.org/release/2.0/UPD/
> > 
> >     openpkg-1.9.3-2.0.3.src.rpm
> >     openpkg-1.9.2-2.0.2.src.rpm [*]
> >     openpkg-1.9.1-2.0.1.src.rpm [*]
> > 
> > [*] belated and just for completeness
> > 
> 
> [...] confused now. What exactly needs to be done to get from OpenPKG
> 1.3.1 to anywhere? [...] Can or should openpkg-1.9.0-2.0.0.src.rpm
> be used at all? Under what circumstances would openpkg-1.9.1-2.0.1,
> openpkg-1.9.2-2.0.2.src.rpm, or openpkg-1.9.3-2.0.3.src.rpm be used?
> 
Maybe it helps you knowing that we at OpenPKG never
- change released packages
- remove released packages

The <name>-<version>-<release> triple is a ultimate identifier for
*released* *source* packages. There are no variants, bugfixes, security
updates, etc. of that package ending up with the same triple. If a
modified package needs to be released the <release> number will be
incremented and a new package is rolled and released. The existing
predecessor package(s) stay dormant on the ftp server.

Regarding the 1.3 -> 2.0 intermediate package 1.9: 

  we take any openpkg-2.0.x-2.0.x.src.rpm
- change the version from 2.0.x to 1.9.x
- remove the Class: header and
- consolidate the class information into the Distribution: header
- remove the %track section (bug: this step omitted in 1.9.0)
- add a human readable note to the %description section and
  end up with openpkg-1.9.x-2.0.x.src.rpm

Only x=0 is in the original release/2.0/SRC directory, 
all x>=1 are placed in the release/2.0/UPD directory, 

>From the http://www.openpkg.org/faq.html:
Q: What should i do if multiple updates within a release exist?
A: Our updates are patched full packages. Just take the latest.

That applies to your specific question as well. Take the latest
openpkg-1.9.x-2.0.x.src.rpm to upgrade to OpenPKG 2.0. To jump directly
to CURRENT you must create your own companion "1.9" as described above.

--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to