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:   31-Jul-2003 16:11:49
  Branch: HEAD                             Handle: 2003073115114800

  Modified files:
    openpkg-re              news.txt

  Log:
    cleanup

  Summary:
    Revision    Changes     Path
    1.21        +55 -154    openpkg-re/news.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/news.txt
  ============================================================================
  $ cvs diff -u -r1.20 -r1.21 news.txt
  --- openpkg-re/news.txt       31 Jul 2003 08:22:06 -0000      1.20
  +++ openpkg-re/news.txt       31 Jul 2003 14:11:48 -0000      1.21
  @@ -10,172 +10,73 @@
     Major changes between OpenPKG 1.2 and OpenPKG 1.3
     =================================================
   
  -    o   hook to support forthcoming OSSP rc which should eventually
  -        replace the OpenPKG "rc" script.  The hook checks if the OSSP rc
  -        is installed and automatically executes it instead of the old
  -        <prefix>/etc/rc. OSSP rc is provided by installing the
  -        "openpkg-rc" package.  This is an early adopters replacement
  -        package only.
  -
  -    o   mangled and partly rewritten OpenPKG "rc" script. It now provides
  -        correct error handing, verbose messages, supports Bourne- and
  -        C-Shell style shells for %env, uses secure temporary file
  -        handling, to name some few majors. Now it comes with a man page.
  -
  -    o   additionally we were also very busy in cleaning up and enhancing
  -        the run-command scripts of all CORE and BASE. We especially
  -        added the long-awaited %status section which soon will allow us
  -        to add smarter starting and stopping of our daemons.
  -
  -    o   log file rotation was hardened for all CORE and BASE packages.
  -        We took care of permissions and daemons will be reloaded,
  -        restarted or use the new fsl jitter option to make sure they
  -        recreate a new log after the previous one was moved. This has
  -        been run-time tested.
  -
  -    o   we added OSSP fsl support for every released package we found to
  -        use syslog(3).
  -
  -    o   OpenPKG Development: in order to make the daily maintainance
  -        less error-prone and time-consuming and to check errors already
  -        in advance for reducing the release engineering efforts, we
  -        recently wrote the so-called "speclint" -- a program which
  -        checks a large amount of syntactical and semantical aspects of
  -        our RPM .spec files.  The same we've now done for the
  -        run-command (rc) and OSSP fsl configuration files with two
  -        additional "linters" named "rclint" and "fsllint". This now
  -        allows us to check mostly all aspects of our packaging input.
  -        Work is now also in progress for an "rpmlint", which checks the
  -        packaging output, the binary .rpm files.
  -
  -    o   OpenPKG Development: to reduce the "line noise" in our CVS
  -        repository, we've added real "mass committing" support to our
  -        developer shell "openpkg-dev". This allowed us to already commit
  -        many mass changes in one clean step this week.  Our
  -        development/packager shell was enhanced again to now provide
  -        even more convinience commands for the PMOD/PSOD.  OpenPKG:
  -        openpkg-dev: we finished the working-off of our internal
  -        "packager shell". It is now fully CVS branch aware and provides
  -        lots simplified and equalized commands. This way the daily
  -        PMOD/PSOD tasks and the security engineering tasks should be
  -        greatly simplified and from now on cost less effort.
  -
  -    o   OpenPKG, MySQL: after a long enough evaluation phase, we've now
  -        officially moved in OpenPKG-CURRENT from MySQL 3.x to MySQL 4.x.
  -        Following our general rules for dealing with versioned packages
  -        (and the fact that we only want _one_ single version in each
  -        release, of course), the old (MySQL-3 based) "mysql" package was
  -        first merged up to 1-STABLE (for possible inclusion into OpenPKG
  -        1.3), then "mysql" was renamed to "mysql3" (in case you still
  -        have to drive MySQL 3 within OpenPKG-CURRENT), "mysql4" become
  -        "mysql" and "mysql4" has gone. Be aware of these changes for
  -        OpenPKG-CURRENT instances
  -
  -    o   OpenPKG: after intensive testing and fixing, we've finally
  -        upgraded in OpenPKG-CURRENT to the current stable GNU C/C++
  -        Compiler Suite (GCC) version 3.3. In case of any occurring
  -        incompatibilities or broken packages, please respond to
  -        [EMAIL PROTECTED] with details.
  -
  -    o   OpenPKG: Request Tracker (RT): we finished the migration from
  -        the Jitterbug based OpenPKG Bug Database to Request Tracker
  -        (RT). For this we've added mandatory HTTPS access and the
  -        bi-directional gatewaying between RT and the mailing-lists
  -        openpkg-dev/openpkg-bugdb. This way, all OpenPKG related
  -        requests now can be found exclusively in the OpenPKG RT and
  -        you're strongly advised to give your OpenPKG feedback to us by
  -        just mailing your request to [EMAIL PROTECTED]
  -        
  -        https://rt.openpkg.org/
  -        mailto:[EMAIL PROTECTED]
  -
  -    o   OpenPKG Service: because the public PGP key servers come and go
  -        (like keyserver.pgp.com) and this way do not allow us to give
  -        out reasonable stable references, we finally solved the problem
  -        by establishing an own OpenPGP and HKP speaking key server for
  -        the OpenPKG community. Additionally, on the key server's website
  -        there is a short step-by-step guideline on how to use GnuPG for
  -        verifying the digital signatures on our RPM packages and
  -        security advisories.
  -        
  -        http://pgp.openpkg.org/
  -        hkp://pgp.openpkg.org/
  -
  -    o   *************************************************************************
  -        ** NOTICE: Now that OpenPKG 1.3 is available, we fully drop support    **
  -        ** for OpenPKG 1.1. Outdated Releases are considered deprecated and no **
  -        ** longer maintained in any way. We especially do no longer provide    **
  -        ** security updates.                                                   **
  -        *************************************************************************
  -
  -  o now all issues are tracked in RT
  -
  -  o release extended to 400 packages
  -
  -  o package upgrades: 400x
  -    Apache 1.3.28, GCC 3.3, ...
  -
  -  o thousands of bugfixes
  -
  -  o ported all packages to over 10 (!) platforms
  -    primary platforms:
  +  o Extended the release size to 400 packages, including important
  +    updates to the latest versions of key applications like Apache
  +    1.3.28, BIND 9.2.2, Binutils 2.14, GCC 3.3, INN 2.4.0, MySQL 4.0.14,
  +    NTP 4.1.2, OpenSSH 3.6.1p2, PostgreSQL 7.3.4, ProFTPd 1.2.8, Samba
  +    2.2.8a, Squid 2.5.3, teTex 2.0.2, Vim 6.2.57.
  +
  +  o Thousands of fixes and improvements.
  +
  +  o Extended official support to 9 platforms and
  +    ported all CORE+BASE+PLUS packages to them. Binary
  +    packages for CORE+BASE are provided, too.
          - FreeBSD 4.8          (ix86)
          - FreeBSD 5.1          (ix86)
          - Debian GNU/Linux 2.2 (ix86)
          - Debian GNU/Linux 3.0 (ix86)
          - RedHat GNU/Linux 9   (ix86)
          - SuSE   GNU/Linux 8.2 (ix86)
  -       - Sun Solaris 2.6      (sparc64)
          - Sun Solaris 8        (sparc64)
  -       - Sun Solaris 8        (ix86)
          - Sun Solaris 9        (sparc64)
          - Sun Solaris 9        (ix86)
  -    secondary platforms:
  +
  +    Additionally, the following platforms are known to work (at
  +    least CORE+BASE and some more), although they are not officially
  +    supported. Binary packages for CORE are provided only.
  +       - FreeBSD 5.1          (alpha)
  +       - Sun Solaris 2.6      (sparc64)
  +
  +    Experimental support for the following platforms exists
  +    at least for bootstrapping and critical CORE packages:
  +       - Sun Solaris 8        (ix86)
          - NetBSD 1.6.1         (sparc64)
  -       - OpenBSD ?
  -       - ...
  -    tertiary platforms:
          - Gentoo Linux 1.4     (ix86)
  -       - MacOS X 10.0.4       (ppc)
   
  -  o GCC 3.3
  -    - ported all packages from vararg to stdarg 
  -    - ported deprecated C++ constructs to current standard
  -
  -  o completely worked off run-command (rc) processor
  -    - better temporary file handling
  -    - %env supports bourne/c-shell
  -    - verbose output
  -    - filtered/captured stdout/stderr of scripts
  -
  -  o completely worked off run-command scripts (rc.*)
  -    - %status
  -    - %stop/%start are %status aware
  -    - opXXX -> rcXXX
  -    - logfile rotations
  -
  -  o OSSP fsl deployment
  -    - doubled number of packages using OSSP fsl
  -    - all support "with_fsl no" to disable OSSP fsl
  -
  -  o Input Linting
  -    - speclint (.spec)
  -    - rclint (rc.*)
  -    - fsllint (fsl.*)
  -   
  -  o Output Linting
  -    - binary .rpm
  -
  -  o bootstrap enhancements:
  -    - fixed/supported {m,r,n,s}uid and {m,r,n,s}gid params
  -    - smaller distribution size
  -    - less requirements (no more uncompress)
  -
  -  o more elaborate openpkg-tool utility
  -
  -  o even more concised and simplified packages by removing even more redundancy
  -    - %{l_value}
  -    - ...
  +  o OpenPKG 1.3 is now fully based on GCC 3.3 only. All CORE+BASE+PLUS
  +    packages were ported to this latest GNU compiler environment,
  +    requiring stricter ISO C and ISO C++ standards compliance by all
  +    applications.
  +
  +  o About 40 syslog(3) based CORE+BASE+PLUS packages (especially
  +    daemons) were enabled to use OSSP fsl (fake syslog library) by
  +    default. Additionally, every package supports buil-time option
  +    "with_fsl no" to disable OSSP fsl logging in case someone prefers
  +    native syslog(3) usage.
  +
  +  o Completely worked off Run-Command (RC) facility, including enhanced
  +    run-command processor and greatly extended run-command usage. Now
  +    all daemon packages at least in CORE+BASE fully support %status and
  +    status-aware %start/%stop/%restart commands and consistently use
  +    logfile rotations. The run-command processor especially now supports
  +    Bourne-Shell and C-Shell outputs on %env commands, verbose messages
  +    and captured stdout/stderr of scripts.
  +
  +  o The quality of the packages has been greatly enhanced by
  +    the rigorous application of fully automated package input and output
  +    checking against OpenPKG guidelines and architectural principles.
  +    All critical aspects are covered, ranging from style to semantical
  +    issues. This not just once enforced the cleanup of packaging,
  +    but also makes sure further development can never fallback. As
  +    a result, the current package specifications are as concise and
  +    redundancy-free as possible. (technically speaking: speclint (for
  +    *.spec), rclint (for rc.*), fsllint (for fsl.*), rpmlint (for binary
  +    *.rpm).
  +
  +  o The continued work on the bootstrapping package resulted in various
  +    enhancements: fixed/supported --{m,r,n,s}uid and --{m,r,n,s}gid
  +    options, smaller distribution size, less run-time requirements (no
  +    more uncompress), etc.
   
     Major changes between OpenPKG 1.1 and OpenPKG 1.2
     =================================================
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to