On Mon, Jun 21, 2004, F. Even wrote: > [...] what I'm asking is, can I do the following: > > Take openpkg-20040609-20040609.src.rpm, modify the spec file as > described earlier to make this a "1.9" bootstrap. Then after > converting the database, I should install the openpkg-20040609- > 20040609.src.rpm again, unmodified, to bring myself from 1.3 to > CURRENT. Is that correct? > ... to bring myself from 1.9 to CURRENT, exactly.
I don't remember all the issues why we introduced the intermediate step. But I do remeber: - OpenPKG 1.3 does not understand the %track section, it will become part of the previous %description. This is a cosmetic issue only. - OpenPKG 1.3 does not understand the Class: header and bails out on rebuilding. This is a showstopper. - The database needs conversion and it's a good idea to do the acutal install with a already converted database but database conversion requires the new rpm. - The new --tagfmt feature requires OpenPKG 2.0 but the upgrade is done using the existing (old) software. This might be a cosmetic issue if you do not use that feature but will be nasty if you use it and the bootstrap package itself receives a wrong filename. The intermediate OpenPKG 1.9 bootstrap resolves all those issues in a very elegant (although CPU time consuming ;-) way and provides a safe and compatible upgrade path. -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
