> 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
>
> See also http://cvs.openpkg.org/chngview?cn=17591 and
> http://cvs.openpkg.org/openpkg-re/upgrade.txt >= 1.44
>
> Thanks for pointing out.
You're welcome. But, not to be bothersome, but I think I'm a little bit
more confused now. What exactly needs to be done to get from OpenPKG
1.3.1 to anywhere? I think this is a little confusing:
- use openpkg-1.3.1 to rebuild and install the
openpkg-1.9.0-2.0.0.src.rpm provided with the 2.0 release
(intentionally no src.sh available). This intermediate package
is a modified openpkg-2.0.0-2.0.0.src.rpm that has the offending
"Class:" header removed. This is the recommended variant.
For updated >= openpkg-2.0.1-2.0.1 corresponding
companion >= openpkg-1.9.1-2.0.1 are available.
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?
Is there any particular path in the bootstrapping I should use if I want
to end up @ CURRENT? Meaning, if I manage to get to openpkg-2.0.0-2.0.0
somehow, someway, can I just short-circuit the rest and install
openpkg-20040609-20040609.src.rpm?
Thanks for your assistance.
Frank
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
