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:   05-Oct-2003 15:36:26
  Branch: HEAD                             Handle: 2003100514362600

  Modified files:
    openpkg-re              news.txt

  Log:
    start assembling the OpenPKG 2.0 news

  Summary:
    Revision    Changes     Path
    1.23        +182 -1     openpkg-re/news.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/news.txt
  ============================================================================
  $ cvs diff -u -r1.22 -r1.23 news.txt
  --- openpkg-re/news.txt       4 Aug 2003 11:27:16 -0000       1.22
  +++ openpkg-re/news.txt       5 Oct 2003 13:36:26 -0000       1.23
  @@ -2,13 +2,194 @@
     General Note
     ============
   
  -  o $Revision: 1.22 $. The most recent update of this file can be
  +  o $Revision: 1.23 $. 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
       improvements. To receive information about tweaks and quirks when
       upgrading, common pitfalls and ways to bypass them read the
       companion upgrade.txt document.
  +
  +  Major changes between OpenPKG 1.3 and OpenPKG 2.0
  +  =================================================
  +
  +  o Extensions to RPM 4.2.1:
  +
  +    --db-{build,rebuild,cleanup,fixate}
  +    accurate removal of temporary files
  +    -bb --short-circuit
  +    ...FIXME...
  +
  +  o Upgraded from RPM 4.0.2 to RPM 4.2.1.
  +
  +    - Query Pattern Matching
  +    
  +      RPM 4.2 now alows a glob(3) pattern matching on queries.
  +      ("rpm -qa kde-*")
  +    
  +    - Platform Identification:
  +    
  +      We finally cleaned up the whole platform identification in RPM. The
  +      new approach now is: <prefix>/lib/openpkg/platform is a program which
  +      dynamically determines the "<arch>-<vendor>-<os>" id string for
  +      the underlying platform. Wxample outputs are: ix86-pc-freebsd4.8,
  +      ix86-pc-redhat9, sparc64-sun-solaris9, etc.
  +    
  +      Then there is <prefix>/etc/openpkg/platform which is the once
  +      determined platform id, loaded by RPM to internally provide the
  +      macros %_host_{cpu,vendor,os} and %_host. Additionally, we adjusted
  +      all other platform id related macros (%_target, %_arch, %_os, etc) to
  +      directly depend on these macros. This way we have a new single point
  +      of source for the official platform id.
  +    
  +    - Bugfixes:
  +    
  +      The upgrade from RPM 4.0.2 (status quo as of March 2001) to RPM 4.2.1
  +      (status quo as of June 2003) is a major code change covering a two
  +      year vendor development cycle. This means hundrets of bugs in RPM
  +      were fixed and the code was partly refactored and cleaned up.
  +    
  +    - Package Signatures:
  +    
  +      RPM 4.2 now uses the BeeCrypt cryptography library for verification
  +      of signatures. Previously one needed an externally available GnuPG.
  +      GnuPG now is only needed for creating signatures. Additionally, RPM
  +      4.2 manages OpenPGP publuc keys in its RPM database similar to real
  +      packages (they even can be seen as pseudo-packages "gpg-pubkey-XXXXX"
  +      under query operations). The OpenPKG bootstrap (and also the regular
  +      upgrade procedure) now especially imports the OpenPKG OpenPGP public
  +      key into this database to make sure that one out-of-the-box can
  +      verify signed packages. Finally, "rpm -qi" now especially displays
  +      signature information, too.
  +    
  +    - RPM Database, Berkeley-DB 4.1.24
  +    
  +      RPM 4.2 now internally uses Berkeley-DB 4.1.24 instead of version
  +      3.2.4 which RPM 4.0 used. The old DB version 7 database files can
  +      still be read without problems and on "openpkg" package upgrade,
  +      the database is rebuilded and upgraded to DB version 8 files
  +      automatically. Additionally, RPM 4.2 now managed more information
  +      than RPM 4.0 and hence uses a few additional database files.
  +    
  +    - Re-Packaging
  +    
  +      RPM 4.2 now provides a nifty --repackage feature which can be applied
  +      especially to the --erase operation. Before erasing the installed
  +      package, RPM then first creates a corresponding binary RPM from
  +      scratch. This later can be used to rollback the erase operation.
  +      It just has to be remembered that the binary RPM resulting from
  +      a "repackage" operation is both not identical to the original
  +      binary RPM (because not all information was installed) and that the
  +      resulting binary RPM usually has a wrong MD5 digest (so you have to
  +      use --nodigest).
  +    
  +    - POPT Upgrade
  +    
  +      RPM 4.2 now uses an enhanced version of the POPT library, which
  +      especially allows special "argument eating" markers "!#:+" to be
  +      used in the rpmpopt file. This allowed us now to provide convinience
  +      macros for %option handling on the command line:
  +    
  +      --with    foo          => --define 'with_foo yes' => %option with_foo yes
  +      --without foo          => --define 'with_foo no'  => %option with_foo no
  +      --option  with_foo bar => --define 'with_foo bar' => %option with_foo bar
  +    
  +    - %files Improvements:
  +    
  +      If the payload contains an OpenPGP public key, it can be added to
  +      the RPM header with a new %files attribute "%pubkey". Additionally,
  +      %exclude will now allow fully exclusion ("everything but"). Then
  +      there is a new %dev(type,major,minor) directive to permit non-root
  +      device files.
  +    
  +    - rpmbuild(8):
  +    
  +      A new command line tool rpmbuild(8) was introduced, providing the
  +      official RedHat way of building packages by accepting all the -bX
  +      options. Those options were removed from the rpm(8) command, too.
  +      OpenPKG provides rpmbuild(8) also, but officially sticks with the
  +      single command approach using just rpm(8) for all operations by
  +      reenabling the legacy option mappings.
  +    
  +    - Verification:
  +    
  +      The "rpm --verify" operation was greatly improved and now checks more
  +      details and is more accurate.
  +    
  +    - Performance:
  +    
  +      Noticable speed improvements were achieved for both query and install
  +      operations.
  +    
  +    - Transactions:
  +    
  +      RPM internally now uses transactions for its operations (implemented
  +      through data structure coloring) and supports full-state rollbacks in
  +      case of problems.
  +
  +    - Concurrency:
  +
  +      RPM internally now uses the Berkeley-DB CDB feature for concurrent
  +      access (read-only and read-write) to the RPM database. This
  +      especially allows RPM packages to act (usually query) on the RPM
  +      database concurrently (e.g. RPM called from within %post, etc)
  +    
  +    - Querying:
  +    
  +      New --queryformat header format modifiers were introduced: ":xml"
  +      for dumping the content in XML (e.g. use --qf '[%{*:xml}\n]' to
  +      dump header content in XML), ":base64" to dump in Base64 format and
  +      ":armor" to dump in hex format.
  +    
  +    - File Classification:
  +    
  +      RPM 4.2 internally now uses the file(3) library for classifying files
  +      and can use this on auto-dependency generation. OpenPKG does not use
  +      this until now.
  +    
  +    - Dependency Solving and Caching:
  +    
  +      Although (still) not used by OpenPKG, RPM 4.2 has some limited
  +      functionality (used by RedHat up2date) to cache binary RPM headers
  +      locally and even store a full separate RPM database with package
  +      information ("rpm --dbpath /path/to/somewhere --justdb -U *.rpm")
  +      and then resolve dependencies through this information. This is
  +      done with the --aid option which implements at least one of the 2
  +      essential elements of a dependency solver. The 2 essential elements
  +      are (a) locate a previously uninstalled package that satisfies a new
  +      dependency. (b) upgrade an already installed package in order to
  +      solve a problem. RPM currently does (a) only.
  +
  +  o New platform identification (%{l_platform})
  +
  +    ...FIXME...
  +
  +  o New release identification (%{l_openpkg_release})
  +
  +    ...FIXME...
  +
  +  o New RPM C API utility "rpm-config"
  +    
  +    ...FIXME...
  +
  +  o Completely worked off Run-Command (RC) facility now also
  +    for PLUS and EVAL packages.
  +  
  +    ...FIXME...
  +
  +  o [TODO] Upgrade to Perl 5.8.1 and fully worked off extensional
  +    Perl module packaging (module search order, vendor_perl, new
  +    perl-openpkg.sh)
  +
  +    ...FIXME...
  +
  +  o [TODO] New website.
  +
  +    ...FIXME...
  +
  +  o thousands of bugfixes ;-)
  +
  +    ...FIXME...
   
     Major changes between OpenPKG 1.2 and OpenPKG 1.3
     =================================================
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to