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 17:00:41
Branch: HEAD Handle: 2004021916004000
Modified files:
openpkg-re news.txt upgrade.txt
Log:
--tag infos
Summary:
Revision Changes Path
1.32 +7 -24 openpkg-re/news.txt
1.26 +21 -4 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/news.txt
============================================================================
$ cvs diff -u -r1.31 -r1.32 news.txt
--- openpkg-re/news.txt 19 Feb 2004 15:22:47 -0000 1.31
+++ openpkg-re/news.txt 19 Feb 2004 16:00:40 -0000 1.32
@@ -2,7 +2,7 @@
General Note
============
- o $Revision: 1.31 $. The most recent update of this file can be
+ o $Revision: 1.32 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/news.txt
o This file news.txt file talks about new features and major
@@ -128,14 +128,9 @@
o new tag feature
- In OpenPKG v1.x, binaries were named
- "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}-%{OS}-%{l_location}.rpm"
- where location was computed during installation of the bootstrap
- and hardcoded for all binaries being build with that bootstrap. The
- prefix of the hierarchy was the input for location id creation.
-
- In OpenPKG v2.x, the location id was replaced by a user
- configurable tag. The tag can be specified during bootstrap
+ In OpenPKG v2.0, binaries are named
+ "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}-%{OS}-%{tag}.rpm" where the
+ tag is user configurable. It tag can be specified during bootstrap
using the new --tag=xxx option. It is then used as a default
for every binary package being build. It can be overridden for
every individual binary package by specifying the --tag=xxx
@@ -149,9 +144,9 @@
More precisely from a users perspective the tag is actually a tag
format (tagfmt). To enhance convenience for the user some predefined
combinations or macros are provided which can be specified using
- their name in angle brackets. The default tagfmt is <compat> (FIXME
- reality currently is <loc>) which provides exactly the same output
- as OpenPKG v1.3 did.
+ their name in angle brackets. The default tagfmt for fresh installs
+ is <loc> which is a improved version of the previous %{l_location}
+ known from OpenPKG v1.x.
Predefined tagfmt's (just omit the %l_tag_fmt_ prefix) are:
@@ -169,18 +164,6 @@
resulting tag can have any character valid for creating a filename
but a dash. No error is created for dashes, they are silently
removed.
-
- Keep in mind the tag feature is a function of the bootstrap that is
- doing the build. An upgrade is run by the existing (old) bootstrap
- which means that the tag feature is not yet available. Unless you're
- hacking the rpmmacros file manually, the easiest way to get the tag
- option on upgrades is to upgrade twice. First to get the new code
- with the new feature but not using it as the build runs with the
- old code. Then once again building the new code, this time with the
- already new code itself, having the feature available.
-
- There is another reason why an intermediate step will be required
- during an upgrade, see "Class" header below.
o new UUID feature
@@ .
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.25 -r1.26 upgrade.txt
--- openpkg-re/upgrade.txt 19 Feb 2004 15:22:48 -0000 1.25
+++ openpkg-re/upgrade.txt 19 Feb 2004 16:00:40 -0000 1.26
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.25 $. The most recent update of this file can be
+ o $Revision: 1.26 $. 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
@@ -134,9 +134,26 @@
o new tag feature to replace location id
- Using an intermediate step during an upgrade allows the new tag
- feature to be engaged for the bootstrap. See "new tag feature" in
- news.txt file.
+ In OpenPKG v1.x, binaries were named
+ "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}-%{OS}-%{l_location}.rpm"
+ where location was computed during installation of the bootstrap
+ and hardcoded for all binaries being build with that bootstrap. The
+ prefix of the hierarchy was the input for location id creation.
+
+ In OpenPKG v2.0, the location id is replaced by a user configurable
+ tag. See "new tag feature" in news.txt file.
+
+ For upgrades the default tag is <compat> to provide full backwards
+ compatiblity to existing %{l_location}.
+
+ The tag feature is a function of the bootstrap that is doing the
+ build. An upgrade is run by the existing (old) bootstrap which means
+ that the tag feature is not yet available. Unless you're hacking the
+ rpmmacros file manually, the easiest way to get the tag option on
+ upgrades is to upgrade twice. First to get the new code with the new
+ feature but not using it as the build runs with the old code. Then
+ once again building the new code, this time with the already new
+ code itself, having the feature available.
o %{l_prefix}/bin/rpm and %{l_prefix}/bin/rpm2cpio deprecated
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
