head 1.48; access; symbols OPENPKG_CW_FP:1.47; locks; strict; comment @# @; 1.48 date 2005.06.22.08.14.49; author thl; state Exp; branches; next 1.47; 1.47 date 2005.02.24.15.54.41; author rse; state Exp; branches; next 1.46; 1.46 date 2004.10.12.11.55.30; author ms; state Exp; branches; next 1.45; 1.45 date 2004.10.11.17.16.05; author ms; state Exp; branches; next 1.44; 1.44 date 2004.07.07.07.54.10; author thl; state Exp; branches; next 1.43; 1.43 date 2004.06.29.07.38.48; author thl; state Exp; branches; next 1.42; 1.42 date 2004.04.19.07.52.56; author thl; state Exp; branches; next 1.41; 1.41 date 2004.03.23.15.56.34; author cs; state Exp; branches; next 1.40; 1.40 date 2004.03.16.19.59.36; author thl; state Exp; branches; next 1.39; 1.39 date 2004.03.16.19.52.08; author thl; state Exp; branches; next 1.38; 1.38 date 2004.02.25.20.47.10; author rse; state Exp; branches; next 1.37; 1.37 date 2004.02.25.10.13.39; author thl; state Exp; branches; next 1.36; 1.36 date 2004.02.24.10.45.50; author thl; state Exp; branches; next 1.35; 1.35 date 2004.02.20.15.18.36; author thl; state Exp; branches; next 1.34; 1.34 date 2004.02.20.14.04.57; author thl; state Exp; branches; next 1.33; 1.33 date 2004.02.20.14.00.35; author rse; state Exp; branches; next 1.32; 1.32 date 2004.02.19.16.00.40; author thl; state Exp; branches; next 1.31; 1.31 date 2004.02.19.15.22.47; author thl; state Exp; branches; next 1.30; 1.30 date 2004.02.17.22.55.35; author thl; state Exp; branches; next 1.29; 1.29 date 2004.02.17.21.49.58; author thl; state Exp; branches; next 1.28; 1.28 date 2004.02.12.11.25.42; author rse; state Exp; branches; next 1.27; 1.27 date 2004.02.06.07.22.09; author rse; state Exp; branches; next 1.26; 1.26 date 2004.01.19.14.21.03; author thl; state Exp; branches; next 1.25; 1.25 date 2004.01.14.08.17.42; author thl; state Exp; branches; next 1.24; 1.24 date 2003.10.05.13.43.03; author rse; state Exp; branches; next 1.23; 1.23 date 2003.10.05.13.36.26; author rse; state Exp; branches; next 1.22; 1.22 date 2003.08.04.11.27.16; author thl; state Exp; branches; next 1.21; 1.21 date 2003.07.31.14.11.48; author rse; state Exp; branches; next 1.20; 1.20 date 2003.07.31.08.22.06; author thl; state Exp; branches; next 1.19; 1.19 date 2003.07.30.12.17.54; author thl; state Exp; branches; next 1.18; 1.18 date 2003.07.29.12.47.29; author ms; state Exp; branches; next 1.17; 1.17 date 2003.07.29.11.34.14; author rse; state Exp; branches; next 1.16; 1.16 date 2003.07.24.07.26.40; author rse; state Exp; branches; next 1.15; 1.15 date 2003.07.23.12.36.02; author rse; state Exp; branches; next 1.14; 1.14 date 2003.01.14.15.25.30; author rse; state Exp; branches; next 1.13; 1.13 date 2002.11.27.08.30.38; author rse; state Exp; branches; next 1.12; 1.12 date 2002.11.27.08.20.30; author thl; state Exp; branches; next 1.11; 1.11 date 2002.11.27.07.49.28; author thl; state Exp; branches; next 1.10; 1.10 date 2002.11.19.08.05.47; author thl; state Exp; branches; next 1.9; 1.9 date 2002.11.19.08.05.26; author thl; state Exp; branches; next 1.8; 1.8 date 2002.11.18.09.16.14; author rse; state Exp; branches; next 1.7; 1.7 date 2002.08.29.09.33.02; author rse; state Exp; branches; next 1.6; 1.6 date 2002.08.28.10.00.17; author rse; state Exp; branches; next 1.5; 1.5 date 2002.08.28.09.38.12; author rse; state Exp; branches; next 1.4; 1.4 date 2002.06.25.11.20.45; author thl; state Exp; branches; next 1.3; 1.3 date 2002.04.30.11.25.11; author thl; state Exp; branches; next 1.2; 1.2 date 2002.04.29.13.10.21; author thl; state Exp; branches; next 1.1; 1.1 date 2002.04.17.11.11.57; author rse; state Exp; branches; next ; desc @@ 1.48 log @add OpenPKG 2.4, reverse sort by date and accent latest paragraph, ISO 8601 dates @ text @ General Note ============ o $Revision: 1.47 $. The most recent update of this file can be downloaded from http://cvs.openpkg.org/openpkg-re/news.txt The history of this document, specific versions and differences between versions can be retrieved from http://cvs.openpkg.org/rlog?f=openpkg-re/news.txt o This file includes changes, new features and major improvements in OpenPKG. For upgrade information such as the most common pitfalls read the release notes at http://cvs.openpkg.org/openpkg-re/relesenotes.txt OpenPKG Release Essentials ========================== o OpenPKG 2.4 (2005-06-22) Latest vendor packages First Release created by the OpenPKG Foundation e.V. o OpenPKG 2.3 (2005-02-24) Latest vendor packages o OpenPKG 2.2 (2004-10-20) Latest vendor packages o OpenPKG 2.1 (2004-07-20) Latest vendor packages, openpkg-tools o OpenPKG 2.0 (2004-02-25) Section %track, Class:, RPM 4.2, shtool platform, OSSP uuid, arbitrary tag string, openpkg-perl.pl+vendor_perl o OpenPKG 1.3 (2003-08-04) GCC 3.3, OSSP fsl (II), worked-off RC facility o OpenPKG 1.2 (2003-01-22) %option, OSSP fsl (I), Perl 5.8, openpkg-perl.sh+site_perl, openpkg-tool o OpenPKG 1.1 (2002-08-28) {s,m,r,n}{usr,grp}, sane build env., with_xxx options, proxy packages o OpenPKG 1.0 (2002-01-11) The initial public release @ 1.47 log @update for release @ text @d5 1 a5 1 o $Revision: 1.46 $. The most recent update of this file can be d18 11 a28 9 o OpenPKG 1.0 (11.01.2002) The initial public release o OpenPKG 1.1 (28.18.2002) {s,m,r,n}{usr,grp}, sane build env., with_xxx options, proxy packages o OpenPKG 1.2 (22.01.2003) %option, OSSP fsl (I), Perl 5.8, openpkg-perl.sh+site_perl, openpkg-tool o OpenPKG 1.3 (04.08.2003) GCC 3.3, OSSP fsl (II), worked-off RC facility o OpenPKG 2.0 (25.02.2004) d31 8 a38 6 o OpenPKG 2.1 (20.07.2004) Latest vendor packages, openpkg-tools o OpenPKG 2.2 (20.10.2004) Latest vendor packages o OpenPKG 2.3 (24.02.2005) Latest vendor packages @ 1.46 log @go back to maintaining RCS version numbers both in CVS and in file contents, to be consistent with openpkg-re/releasenotes.txt (and maybe other files as well) @ text @d31 3 a33 1 o OpenPKG 2.2 (**.**.****) @ 1.45 log @edit and prepare news for OpenPKG 2.2 @ text @d5 5 a9 2 o The most recent update of this file can be downloaded from http://cvs.openpkg.org/openpkg-re/news.txt @ 1.44 log @consolidate news.txt and upgrade.txt into new releasenotes.txt moving content verbatim; news.txt retains some high level overview information, upgrade.txt is completely obsolete @ text @d5 2 a6 2 o $Revision: 1.43 $. The most recent update of this file can be downloaded from http://cvs.openpkg.org/openpkg-re/news.txt d8 3 a10 5 o This file news.txt file briefly lists changes, new features and major improvements. To receive more information and hints about tweaks and quirks when upgrading, common pitfalls and ways to bypass them read the "Release Notes" document which can be downloaded from http://cvs.openpkg.org/openpkg-re/relesenotes.txt d12 2 a13 2 Essentials about Releases ========================= d15 15 a29 6 o OpenPKG 1.0: the initial public release o OpenPKG 1.1: {s,m,r,n}{usr,grp}, sane build env., with_xxx options, proxy packages o OpenPKG 1.2: %option, OSSP fsl (I), Perl 5.8, openpkg-perl.sh+site_perl, openpkg-tool o OpenPKG 1.3: GCC 3.3, OSSP fsl (II), worked-off RC facility o OpenPKG 2.0: %track, Class:, RPM 4.2, shtool platform, OSSP uuid, tags, openpkg-perl.pl+vendor_perl o OpenPKG 2.1: latest vendor packages, openpkg-tools added @ 1.43 log @start working on news and upgrade information about OpenPKG 2.1 @ text @d5 1 a5 1 o $Revision: 1.42 $. The most recent update of this file can be d8 5 a12 4 o This file news.txt file talks about new features and major improvements. To receive information about tweaks and quirks when upgrading, common pitfalls and ways to bypass them read the companion upgrade.txt document. d22 1 a22 878 Essentials about OpenPKG 2.1 ============================ o Latest Vendor Packages as of Jun 2004 o Supported Platforms (HPUX, NetBSD, Mandrake) o New openpkg-tools package o Dropped legacy commands o Debian 3.1 (sarge) install-info issue solved o Some workarounds for known OpenPKG 2.0 issues still apply Major changes between OpenPKG 2.0 and OpenPKG 2.1 ================================================= o Vendor Refresh Release This OpenPKG release is a refresh to its predecessor containing the latest vendor packages. o Supported Platforms OpenPKG 2.1 classifies the following platforms "supported" which means all CORE+BASE+PLUS sources work and CORE+BASE binaries are available. ix86-debian3.0 Debian GNU/Linux 3.0 ix86-fedora2 RedHat Fedora Core 2 ix86-freebsd4.10 FreeBSD 4.10-STABLE ix86-freebsd5.2 FreeBSD 5.2-CURRENT ix86-rhel3 RedHat Enterprise Linux 3 ES ix86-solaris9 Sun Solaris 9/x86 ix86-suse9.1 SuSE Linux 9.1 sparc64-solaris8 Sun Solaris 8 sparc64-solaris9 Sun Solaris 9 (Forte-C) OpenPKG 2.1 classifies support for the following platforms "tentative" which means all CORE sources work, most BASE+PLUS sources work and only CORE binaries available. alpha-freebsd5.2 FreeBSD 5.2-CURRENT hppa-hpux11.11 HP UX 11.11 ix86-debian3.1 Debian GNU/Linux 3.1-pre ix86-gentoo1.4.16 Gentoo Linux 1.4.16 ix86-mandrake10.0 Mandrake Linux 10 ix86-netbsd1.6.2 NetBSD 1.6.2 ix86-solaris10 Sun Solaris 10/x86 sparc64-netbsd1.6.2 NetBSD 1.6.2 sparc64-solaris10 Sun Solaris 10 OpenPKG 2.1 classifies support for the following platforms "obsolete" which means all CORE sources work, most BASE+PLUS sources work and only CORE binaries available. ix86-rhl9 RedHat Linux 9 ix86-suse9.0 SuSE Linux 9.0 sparc64-solaris2.6 Sun Solaris 2.6 OpenPKG 2.1 does not come with binaries for other platforms. No binaries are provided for PLUS packages. Updates are only available as source packages. Packages with a class different from CORE, BASE, PLUS are not part of the release. They are only available as CURRENT source packages. o New openpkg-tools package This new package provides tools for administrators and developers. o Dropped legacy commands The official command line user interface to rpm is the %{l_prefix}/bin/openpkg command multiplexer with the "rpm" subcommand. The direct execution of %{l_prefix}/bin/rpm is no longer available. For more information see "%{l_prefix}/bin/rpm and %{l_prefix}/bin/rpm2cpio deprecated" in the OpenPKG 2.0 section of the upgrade.txt file. o Debian 3.1 (sarge) install-info issue solved The hack described for OpenPKG 2.0 is no longer required. o Some workarounds for known OpenPKG 2.0 issues still apply - issue with RedHat FC1 and EL3 - issue with RedHat Enterprise Linux 3 nptl-devel package - issue with RedHat Fedora Core 1 /proc/sys/kernel/exec-shield Essentials about OpenPKG 2.0 ============================ o Major Release o Bootstrap Package ("openpkg"): - upgraded from RPM 4.0.4 to RPM 4.2.1 - new RPM DB format (upgrade from Berkeley DB 3.2 to 4.1) - new RPM DB administration utility (--db-{build,rebuild,cleanup,fixate}) - new RPM DB locking on network storage requires NFS lockd or locking needs to be disabled - RPM now is able to verify package signatures internally (via BeeCrypt) - RPM now provides "rpm -e --repackage" functionality - more accurate removal of all temporary build files - new "rpm -bb --short-circuit" - "rpm -bs" no longer requires source dependencies - new "%track" section replaces vc.* files - new "%test" section test [unused, reserved for future use] for quality assurance - new "Class:" header (for CORE,BASE,PLUS,EVAL,JUNK tagging) - new platform identification (via our GNU shtool 2.0's new 'platform' command) - platform and instance identification via UUID (via our new OSSP uuid toolkit) - new convenience CLI options "--with " and "--without " - RPM now internally uses transactions - RPM now is able to perform concurrently (allowing RPM to be called from RPM) - many of the CORE packages are OpenPKG "branded" now - the RPM C API is installed and available via "rpm-config" utility - new --tar option eases extraction of shell archive ingredients aiding recovery activities o Upgraded to Perl 5.8.3 and completely worked off Perl module packaging (perl-openpkg) o Completely worked off Run-Command (RC) facility now also for PLUS and EVAL class packages. o All packages were upgraded to their latest vendor versions as of YX-Feb-2004. o Increased release class packages from 400 (in OpenPKG 1.3) to now 473 o Thousands of packaging bugfixes and vendor source code portations Major changes between OpenPKG 1.3 and OpenPKG 2.0 ================================================= o Major Release OpenPKG release numbering is driven by technical enhancements and release engineering requirements, not by marketing. The technical change is that we now have RPM 4.2.1 under the hood. The typical administrator knowing OpenPKG 1.3 will experience a flat learning curve when he starts working with the new 2.0 release. o Supported Platforms OpenPKG 2.0 fully supports the following platforms and provides binaries of packages from the CORE+BASE classes. ix86-freebsd4.9 FreeBSD 4.9 ix86-freebsd5.2 FreeBSD 5.2 ix86-debian3.0 Debian GNU/Linux 3.0 ix86-debian3.1 Debian GNU/Linux 3.1 ix86-fedora1 Red Hat Fedora Core 1 ix86-rhel3 Red Hat Enterprise Linux 3 ix86-suse9.0 SuSE Linux 9.0 ix86-solaris9 Sun Solaris 9 sparc64-solaris8 Sun Solaris 8 sparc64-solaris9 Sun Solaris 9 ix86-solaris10 Sun Solaris 10 OpenPKG 2.0 also supports the following platforms and provides binaries of packages from the CORE class. ix86-debian2.2 Debian GNU/Linux 2.2 ix86-rhl9 Red Hat Linux 9 ix86-suse8.2 SuSE Linux 8.2 ix86-gentoo1.4.3 Gentoo Linux 1.4 sparc64-solaris2.6 Sun Solaris 2.6 OpenPKG 2.0 does not come with binaries for other platforms. No binaries are provided for PLUS packages. Updates are only available as source packages. Packages with a class different from CORE, BASE, PLUS are not part of the release. They are only available as CURRENT source packages. o new prefix and tag for binary packages OpenPKG 2.0 comes with binaries build for /openpkg prefix and openpkg tag. Previously they were build for /cw prefix and locationid (the predecessor of tag) cw. This is meaningless to the admin who never uses binary packages according to OpenPKG recommendation. For those installing binary packages from OpenPKG version 2.0 and later, attention should be given to this change. For example, scripts installing OpenPKG 2.0 binary packages and later expecting the resulting software to be available in '/cw' will now fail. o new command line interface The official command line user interface to rpm is the new %{l_prefix}/bin/openpkg command multiplexer with the "rpm" subcommand. The direct execution of %{l_prefix}/bin/rpm is deprecated. For more information see "%{l_prefix}/bin/rpm and %{l_prefix}/bin/rpm2cpio deprecated" in upgrade.txt file. o new RPM header - Class: header to specify status, one of CORE,BASE,PLUS,EVAL,JUNK See http://cvs.openpkg.org/chngview?cn=14532 o new RPM sections - %track contains version tracking information and replaces vc.* files previously stored in separate files in the release engineering area of the CVS repository. $ %{l_prefix}/bin/openpkg rpm --track - %test [unused, reserved for future use] for quality assurance. $ %{l_prefix}/bin/openpkg rpm --test o new tag feature In OpenPKG 2.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 option on a --rebuild or -bb or -ba command line. See http://cvs.openpkg.org/chngview?cn=14312 The tag is even more powerful as it is not a constant string but a macro that is expanded during the build process. This allows for creation of dynamic tags. 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 for fresh installs is 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: - %l_tag_fmt_compat location id (compatible to OpenPKG v1.x) - %l_tag_fmt_loc location id (improved) - %l_tag_fmt_opt UUID based on with_xxx options - %l_tag_fmt_uuid UUID - %l_tag_fmt_time date and time of build - %l_tag_fmt_user user doing the build - %l_tag_fmt_host host that run the build The predefined tagfmt's are not limits, just examples. Use any combination of predefined tags, RPM macros and constants to create a tagfmt, i.e. "binaryat