On Thu, Apr 01, 2004, Dennis McRitchie wrote:
> I am currently running in an openpkg-20031020 environment. I'm trying to do
> a minimal 2.0 upgrade that will
> 1) allow me to build new 2.0 packages without having to hack the Class tag
> out of the spec files, but
> 2) also allow me to avoid rebuilding the world.
Then do the following:
1. remove openpkg-tool
2. upgrade to the latest "openpkg" from CURRENT by installing
("rpm -Uvh") the openpkg*.src.rpm, removing the Class header once
("vi openpkg.spec"), doing a "rpm -bb" and installing with with "rpm
-Uvh" and this way upgrading the bootstrap package from 20031020 to
200403xx. The "openpkg rpm --db-rebuild" I recommend you, because it
will not destroy anything and makes sure you are consistent in your
database. If you are sceptic, just backup <prefix>/RPM/DB/ before.
3. reinstall openpkg-tool
> Could I accomplish this with the following:
>
> 1) Remove openpkg-tool.
> 2) Build and install openpkg-1.9.0-2.0.0
> 3) Skip "openpkg rpm --db-rebuild" since openpkg-20031020 is already using
> RPM 4.2.1.
> 4) Avoid upgrading perl-openpkg at all costs! :-)
> 5) No need to rebuild and install openpkg-2.0.0 since I plan to keep the
> location tag in compatibility mode.
> 6) Reinstall openpkg-tool.
Yes, will work. But if you run CURRENT and want to still run CURRENT,
there is no need to jump through the release version of the "openpkg"
package.
> If I understood the upgrade documentation correctly, I should now be able
> to:
> 1) continue to run all packages that were installed prior to the upgrade,
> 2) rebuild any pre-2.0.0 packages that I already have in my repository
> (including perl-* packages), and
> 3) build any 2.0 packages with the exception of perl-* packages.
>
> Is that right?
Yes.
> Alternately, if I were to upgrade perl-openpkg, I would now be unable to
> rebuild any pre-2.0.0 perl-* packages, but be able to build 2.0 perl-*
> packages.
Yes.
> However, in this case, could I continue to *run* any already
> installed pre-2.0 perl-* packages (as long as I don't try to rebuild and
> reinstall them) along with any newly built and installed 2.0 perl-*
> packages?
> [...]
Yes, even if your "perl" version is different, because Perl
automatically finds modules also in older versioned directories.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
