On Sun, Jun 20, 2004, F. Even wrote:
> I'm currently running OpenPKG 1.3. I'm in the process of upgrading my
> FreeBSD 4.0 box to OpenPKG 2.0. I'm noticing on the release schedule
> that OPKG 2.1 should be out shortly. Is there any reason, considering
> this, that I shouldn't just upgrade to OPKG-current? ...and if I were
> to do that, are there any specific processes I should follow?
>
> I'm thinking:
>
> 1. Install openpkg-1.9.0-2.0.0.src.rpm
> 2. Upgrade to openpkg-2.0.0-2.0.0.src.rpm
> 3. Upgrade to openpkg-2.0.3-2.0.3.src.rpm (should I apply the 2.0.1 -
> 2.0.2 versions first?)
No, just directly use 2.0.3-2.0.3 after 1.9.0-2.0.0.
No need to go through the intermediate versions.
> 4. Upgrade installed pkgs to 2.x.x versions.
> 5. Install openpkg-20040609-20040609.src.rpm
> 6. Upgrade installed pkgs to "current" versions.
> 7. Wait for OPKG 2.1 release and upgrade to that.
>
> Is there any problems with this scenario?
No, will work. But I don't think it is reasonable to go to 2.0, then to
CURRENT as of today and then to 2.1 because this way you are jumping
between releases and CURRENT. For a few particular packages this is ok,
but for a whole OpenPKG instance I wouldn't do this. So, I recommend you
to upgrade now from 1.3 to 2.0 and once 2.1 is out (within a few weeks)
just upgrade to 2.1. For CURRENT my personal rule is: either stick 100%
with CURRENT throughout an OpenPKG instance (i.e. all packages or from
CURRENT and you are upgrading to the latest CURRENT packages all the
time) or use a release throughout the OpenPKG instance and CURRENT only
for a few selected packages (most of the time because you want even more
bleeding edge versions for them).
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
