OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-re                       Date:   12-Feb-2004 12:25:42
  Branch: HEAD                             Handle: 2004021211254200

  Modified files:
    openpkg-re              news.txt

  Log:
    remember a few more details

  Summary:
    Revision    Changes     Path
    1.28        +43 -4      openpkg-re/news.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/news.txt
  ============================================================================
  $ cvs diff -u -r1.27 -r1.28 news.txt
  --- openpkg-re/news.txt       6 Feb 2004 07:22:09 -0000       1.27
  +++ openpkg-re/news.txt       12 Feb 2004 11:25:42 -0000      1.28
  @@ -2,7 +2,7 @@
     General Note
     ============
   
  -  o $Revision: 1.27 $. The most recent update of this file can be
  +  o $Revision: 1.28 $. 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
  @@ -10,6 +10,44 @@
       upgrading, common pitfalls and ways to bypass them read the
       companion upgrade.txt document.
   
  +  Essentials about Releases
  +  =========================
  +
  +  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 plaform, OSSP uuid, tags, 
openpkg-perl.pl+vendor_perl
  +
  +  Essentials about OpenPKG 2.0
  +  ============================
  +
  +  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})
  +    - 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 (containing the vcheck(1) configs) and "rpm --track"
  +    - new "%test" section (for forthcoming test suites) and "rpm --test"
  +    - 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 convinience CLI options "--with <name>" and "--without <name>"
  +    - RPM now internally uses transactions
  +    - RPM now is able to perform concurrently (allowing RPM to be called from RPM)
  +    - most of the CORE packages are OpenPKG "branded" now
  +    - the RPM C API is installed and available via "rpm-config" utility
  +  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 474 
  +  o Increased number of supported platforms to XX
  +  o Thousands of packaging bugfixes and vendor source code portations
  +
     Major changes between OpenPKG 1.3 and OpenPKG 2.0
     =================================================
   
  @@ -18,9 +56,10 @@
       OpenPKG version 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 engineering
  -    changes are the discontinuation of a STABLE branch and SNAPSHOTs.
  -    The typical administrator knowing OpenPKG 1.3 will experience a flat
  -    learning curve when he starts working with the new 2.0 release.
  +    changes are (for the time being) the discontinuation of a STABLE
  +    branch and SNAPSHOTs. The typical administrator knowing OpenPKG 1.3
  +    will experience a flat learning curve when he starts working with
  +    the new 2.0 release.
   
     o Extensions to RPM 4.2.1:
   
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to