OpenPKG CVS Repository http://cvs.openpkg.org/ ____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer Root: /v/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-re Date: 12-May-2006 22:02:46 Branch: HEAD Handle: 2006051221024400 Modified files: openpkg-re releasenotes.txt Log: registry news Summary: Revision Changes Path 1.19 +28 -4 openpkg-re/releasenotes.txt ____________________________________________________________________________ patch -p0 <<'@@ .' Index: openpkg-re/releasenotes.txt ============================================================================ $ cvs diff -u -r1.18 -r1.19 releasenotes.txt --- openpkg-re/releasenotes.txt 19 Oct 2005 09:16:35 -0000 1.18 +++ openpkg-re/releasenotes.txt 12 May 2006 20:02:44 -0000 1.19 @@ -2,7 +2,7 @@ OpenPKG Release Notes ===================== - o $Revision: 1.18 $. The most recent update of this file can be + o $Revision: 1.19 $. The most recent update of this file can be downloaded from http://cvs.openpkg.org/openpkg-re/releasenotes.txt The history of this document, specific versions and differences between versions can be retrieved from @@ -52,6 +52,27 @@ life. Continuing to run outdated release packages not within the aforementioned security range introduces risks. + New past OpenPKG 2.5 + ==================== + + o Registry + + In November 2005, after the release of OpenPKG 2.5, the Registry was + introduced. The client part to register and to rewrite rpm URLs was made + available as a CURRENT package with openpkg-registry-0.3.0 being the most + widespread in use for roughly half a year. Beginning with bootstrap + openpkg-20060512 the client part became embedded and did no longer require + the use of a extra package. Coexistence of a modern bootstrap with a + external package is not recommended but possible with the following ceveat: + a bug in openpkg-registry-0.3.0 causes the "register" command to + accidentally call rpm where it should have called itself. This causes + strange error messages regarding unsupported register options. The rpm URL + rewriting still continues to work and allows the instance to operate and to + upgrade packages. It is necessary to upgrade to openpkg-registry-0.4.1 or + later to fix the problem. It is recommended to erase the openpkg-registry + package because the whole functionality is embedded in the bootstrap + anyway. + New in OpenPKG 2.5 ================== @@ -1316,9 +1337,12 @@ 1 0 1 N/A 1 1 0 OpenPKG v1.x with openpkg-tool installed 1 1 1 OpenPKG 2.0 with /bin/rpm compatibility wrapper - - 1 x 0 OpenPKG v1.x - x 1 1 OpenPKG v2.x + + /lib/openpkg/rpm + | + 1 x 0 1 OpenPKG v1.x + x 1 1 0 OpenPKG v2.x + x 1 1 1 OpenPKG v2.x with embedded registry url rewriter o %{l_prefix}/bin/openpkg vs. openpkg-tool @@ . ______________________________________________________________________ The OpenPKG Project www.openpkg.org CVS Repository Commit List openpkg-cvs@openpkg.org