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: 19-Feb-2004 10:56:00
Branch: HEAD Handle: 2004021909560000
Modified files:
openpkg-re todo.txt upgrade.txt
Log:
clear item; log how the version=release problem was solved
Summary:
Revision Changes Path
1.188 +1 -2 openpkg-re/todo.txt
1.24 +61 -2 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/todo.txt
============================================================================
$ cvs diff -u -r1.187 -r1.188 todo.txt
--- openpkg-re/todo.txt 18 Feb 2004 10:04:01 -0000 1.187
+++ openpkg-re/todo.txt 19 Feb 2004 09:56:00 -0000 1.188
@@ -41,12 +41,11 @@
<done>
SHOULD HAVE:
+ <done>
NICE TO HAVE:
o rse: companion GNU shtool 2.0.0 (DONE FOR 2.1)
o rse: GCC 3.3.3? (DONE FOR 2.1)
- o Version: %{release} deploy: problems! -> openpkg build! Release: %{version}
XX, Version: %(rpm -q --qf '%release' *.spec)) [thl]
- (see RSE's check-version script)
o speclint.pl to check %build for BUILDROOT removal (now possible as new
perl-openpkg removed exceptions)
o dig into problem where file conflicts are not detected
o "plus in release" bug leads to double installations
@@ .
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.23 -r1.24 upgrade.txt
--- openpkg-re/upgrade.txt 17 Feb 2004 14:09:50 -0000 1.23
+++ openpkg-re/upgrade.txt 19 Feb 2004 09:56:00 -0000 1.24
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.23 $. The most recent update of this file can be
+ o $Revision: 1.24 $. 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
@@ -246,7 +246,8 @@
"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
+ to provide additional subcommands to be plugged in and overload
+ default subcommands. 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
@@ -263,6 +264,64 @@
20$ openpkg man index #FIXME openpkg man not implemented as of 20040217
20$ openpkg man build #FIXME openpkg man not implemented as of 20040217
+ o packages dropped from release (FIXME check for completeness)
+
+ - openpkg-tool is available as CURRENT package
+
+ o package version numbering changes
+
+ OpenPKG uses a package naming scheme that starts with
+ <name>-<version>-<release>. Details can be reviewed at
+ http://www.openpkg.org/cvs.txt, they did not change although OpenPKG
+ never used snapshots and OpenPKG v2.0 makes no attempt to use a
+ SOLID branch. The version part is usually directly inherited from
+ the vendor version. There were always some packages where a vendor
+ version was not available. Examples are those that only reference
+ OS components (i.e. x11), bundle multiple vendor versions (i.e.
+ perl-*, infozip) and metapackges which only provide requirements.
+ In OpenPKG v1.x these packages had version=release both in CURRENT
+ (i.e. perl-conv-20040207-20040207.src.rpm) and RELEASE (i.e.
+ perl-comp-1.3.0-1.3.0.src.rpm). This is redundant information that
+ made release engineering unnessessary hard. Adjusting the version
+ was a manual and error prone task. In fact OpenPKG v1.3 had such
+ a bug and the pam-20030715-1.3.0.src.rpm package had the version
+ unchanged by accident. This eventually triggered the following
+ changes in OpenPKG v2.x:
+
+ - Packages that only reference existing OS components
+ have the version changed to constant zero, see
+ http://cvs.openpkg.org/chngview?cn=14942
+
+ kde meta-* openpkg-import oracle pam sgml x11
+
+ - Packages with perl modules belong to Perl and have the version
+ changed to that of the perl package they belong to, see
+ http://cvs.openpkg.org/chngview?cn=14937
+
+ perl-*
+
+ - Packages which are bundles that have no real "master" version;
+ first solution: concatenate versions, see
+ http://cvs.openpkg.org/chngview?cn=14938
+
+ infozip
+
+ - Packages which are bundles that have no real "master" version;
+ second solution: manually maintain version only (only is new)
+ whenenver one of the vendor version changes.
+
+ openpkg-tool, kolab
+
+ In all cases of packages and branches the release is now maintained
+ independent of the version.
+
+ Some these changes might make RPM think it performes a downgrade, so
+ --oldpackage might be required during an upgrade. Example:
+
+ 13> pam-20030715-1.3.0.src.rpm (accident)
+ 13> pam-1.3.1-1.3.1.src.rpm
+ 20> pam-0-2.0.0.src.rpm
+
Upgrade from OpenPKG 1.2 to OpenPKG 1.3
=======================================
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
