On Tue, Feb 17, 2004, Ralf S. Engelschall wrote:
> Currently, the following [...] issues [...]
>
Based on our experiences with deploying early adopters CURRENT packages
in our labs, build farm, development environment and selected live
setups let me add a 30000ft view of the critical issues you will be
facing during the upgrade process.
- upgrade to openpkg-1.3.1 (if not already done)
- upgrade openpkg-1.3.1 to intermediate openpkg-20040130
- rebuild rpm database (extra considerations when DB store on NFS)
- choose favorite --tag usage and use/apply
- erase openpkg-tool-1.3
- upgrade openpkg-20040130 to openpkg-2.0.0 (or openpkg-20040217 ...)
- install openpkg-tool-2.0 (or openpkg-tool-20040217 ...)
- reflect "rpm" to "openpkg rpm" change in your scripts, docs and habits
My attempt to justify the intermediate step:
The intermediate step uses a bootstrap that offers the new --tag
option and supports the new Class: header but does not use these new
features. It uses the legacy rpm command location and has no file
conflicting with openpkg-tool. This allows older bootstraps to build
the intermediate. It also allows the intermediate to build the newer
bootstraps.
Avoid running the intermediate for prolonged times. It should be able
to run a 1.3.1 environment (i.e. rc) but was not extensively tested.
It's what the name suggests: a intermediate step in the upgrade process.
Don't install Fridays and leave the office till Monday ;-)
For details see
http://cvs.openpkg.org/openpkg-re/news.txt
http://cvs.openpkg.org/openpkg-re/upgrade.txt
The content of these files is almost complete although prose and format
is not pretty.
--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
