Just a HEADS UP to those of you who are running OpenPKG-CURRENT as of
these days: In preparation for OpenPKG 2.0 we have decided to finally
switch to the namespace cleaned up filesystem layout in the bootstrap
package "openpkg". The short-term goal is to make OpenPKG bootstrap
package namespace clean (the "openpkg" command is the ONLY frontend
to all OpenPKG management commands) and this way have the "cut" only
between 1.x and 2.0 (and not between 2.0 and 2.1 where it is not
acceptable), but the long-term goal is to provide the bootstrap part of
the new forthcoming OpenPKG Tool Chain (developed between 2.0 and 2.1)
in a way we then can seamlessly integrate it into the bootstrap package.
The key point is the new %{l_prefix}/bin/openpkg command. This is
already known from the old (and soon replaced) "openpkg-tool" package
(although it is completely different implementation). It is now part
of the "openpkg" package and all management commands are now reachable
through "openpkg <command>" only. This includes the "rpm" command, too!
It is now "openpkg rpm". Yes, we know that this breaks habits of admins
and was not an easy decision, but we have finally to do it now with
OpenPKG 2.0, because that's for what _major_ OpenPKG versions are for.
For smart migration reasons we still provide the "rpm" and "rpm2cpio"
commands in 2.0 under <prefix>/bin/, but they now output a warning
before running the corresponding "openpkg rpm" and "openpkg rpm2cpio"
commands. In 2.1 they will be finally removed at all). So, don't be
confused in advance. All this will be well documented in detail in the
"upgrade" document for OpenPKG 2.0. But if you use CURRENT you slide
into this these days seamlessly without notice. Currently, the following
two issues exist for you:
1. If you are still running "openpkg < 20040130", you are faced
with the fact that your installed RPM does still not understand
the "Class" headers which are now in all CURRENT packages.
For this either build and install the "intermediate upgrade"
package "openpkg-20040130-20040130.src.rpm" you find in
ftp://ftp.openpkg.org/contrib/. After this you can build and install
the latest "openpkg" package as usual.
2. If you running "openpkg < 20040217" and the "openpkg-tool" package,
you are faced with the fact that the latest "openpkg" conflicts
(in files) with your installed "openpkg-tool" and the latest
"openpkg-tool" requires a more recent "openpkg". Deadlock! But the
easy solution is to just remove "openpkg-tool" first, then upgrade to
the latest "openpkg" and then reinstall the latest "openpkg-tool".
Sorry, we know that those things are inconvinient during the current
OpenPKG 2.0 transition phase. OTOH those changes are what you have to
expect if you're running CURRENT ;-) And people upgrading from 1.3 to
2.0 will be faced with the same in a few days, although they can be
better teached how to perform the upgrade 100% smoothly...
So, if you're running CURRENT, its now time to solve the above two
points by upgrading to the latest "openpkg" and "openpkg-tool" packages.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
