Hi,
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.
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.
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?
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. 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?
The reason for my questions is that we will only be deploying upgraded (as
opposed to new) packages to the University community semi-annually, and it
would be nice to avoid having to keep on hacking spec files until the
summer.
Thanks for your help.
Thanks,
Dennis
Dennis McRitchie
Research & Academic Applications Support (RAAS)
Academic Services Department
Office of Information Technology
Princeton University
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
