OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 17-Feb-2004 15:09:50
Branch: HEAD Handle: 2004021714095000
Modified files:
openpkg-re upgrade.txt
Log:
add information about new openpkg subcommand multiplexer
Summary:
Revision Changes Path
1.23 +65 -1 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.22 -r1.23 upgrade.txt
--- openpkg-re/upgrade.txt 3 Feb 2004 09:14:47 -0000 1.22
+++ openpkg-re/upgrade.txt 17 Feb 2004 14:09:50 -0000 1.23
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.22 $. The most recent update of this file can be
+ o $Revision: 1.23 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.txt
o This file upgrade.txt file talks about tweaks and quirks when
@@ -198,6 +198,70 @@
There is another reason why an intermediate step will be required
during an upgrade, see "tag" feature above.
+
+ o %{l_prefix}/bin/rpm and %{l_prefix}/bin/rpm2cpio deprecated
+
+ Direct execution of %{l_prefix}/bin/rpm and %{l_prefix}/bin/rpm2cpio
+ is deprecated. The binaries were relocated. Switch to using the new
+ %{l_prefix}/bin/openpkg command multiplexer and use the appropriate
+ subcommand, i.e.
+
+ $ /13/bin/rpm -qi openpkg
+ $ /20/bin/openpkg rpm -qi openpkg
+
+ OpenPKG v2.0 provides a wrapper for "rpm" and "rpm2cpio" to be found
+ at the well known locations. They provide a compatible interface and
+ ensure existing automation scripts can be used unaltered. However,
+ every call to these legacy wrappers yields a big three line WARNING
+ to STDERR. Please note that OpenPKG v2.1 will discontinue support
+ for these wrappers and any legacy application will fail unless it is
+ properly updated.
+
+ o supporting calls to rpm in both OpenPKG v1.x and 2.x
+
+ Developers note that checking for bin/openpkg and libexec/openpkg
+ is necessary to detect 2.x because 1.x provided an incompatible
+ bin/openpkg through the openpkg-tool package
+
+ /bin/rpm
+ | /bin/openpkg
+ | | /libexec/openpkg
+ | | |
+ 0 0 0 no OpenPKG installed
+ 0 0 1 N/A
+ 0 1 0 N/A
+ 0 1 1 OpenPKG v2.1 (and later)
+ 1 0 0 OpenPKG v1.x w/o openpkg-tool
+ 1 0 1 N/A
+ 1 1 0 OpenPKG v1.x with openpkg-tool installed
+ 1 1 1 OpenPKG v2.0 with /bin/rpm compatiblity wrapper
+
+ 1 x 0 OpenPKG v1.x
+ x 1 1 OpenPKG v2.x
+
+ o %{l_prefix}/bin/openpkg vs. openpkg-tool
+
+ In OpenPKG v1.x a %{l_prefix}/bin/openpkg subcommand multiplexer was
+ provided as part of the openpkg-tool package. It had two subcommands
+ "index" and "build". In OpenPKG v2.x the %{l_prefix}/bin/openpkg
+ multiplexer was rewritten from scratch and became part of the
+ bootstrap. It's power comes from the fact that it allows packages
+ to provide additional subcommands to be plugged in. Because the
+ old openpkg-tool and the new bootstrap provide the same file they
+ conflict with each other and their use is mutually exclusive. It is
+ therefore imperative to erase the old openpkg-tool package before
+ upgrading. After the upgrade a new openpkg-tool package can be
+ installed which was revamped to provide "index" and "build" plug
+ ins. This effectively hides the change for normal use, i.e.
+
+ $ /13/bin/openpkg build -Ua
+ $ /20/bin/openpkg build -Ua
+
+ However, access to the manual page(s) changed
+
+ 13$ man openpkg
+ 20$ openpkg man index #FIXME openpkg man not implemented as of 20040217
+ 20$ openpkg man build #FIXME openpkg man not implemented as of 20040217
Upgrade from OpenPKG 1.2 to OpenPKG 1.3
=======================================
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
