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:   06-Feb-2004 08:39:59
  Branch: HEAD                             Handle: 2004020607395900

  Modified files:
    openpkg-re/vcheck       00README
  Removed files:
    openpkg-re/vcheck       00TODO

  Log:
    reduce even more

  Summary:
    Revision    Changes     Path
    1.4         +4  -18     openpkg-re/vcheck/00README
    1.8         +0  -17     openpkg-re/vcheck/00TODO
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/vcheck/00README
  ============================================================================
  $ cvs diff -u -r1.3 -r1.4 00README
  --- openpkg-re/vcheck/00README        18 Mar 2002 08:51:43 -0000      1.3
  +++ openpkg-re/vcheck/00README        6 Feb 2004 07:39:59 -0000       1.4
  @@ -1,20 +1,6 @@
   
  -  This is the version checking area of OpenPKG release engineering. It
  -  contains various vcheck(1) configurations (vc.*) which are used to
  -  check for the latest versions of OpenPKG packages. To run this stuff
  -  you have to install the OpenPKG "vcheck" package or use a locally
  -  installed vcheck from http://www.tu-ilmenau.de/~gomar/stuff/vcheck/
  -
  -  Notice that a openpkg-re/vcheck/vc.xxx file at any time have to cover the
  -  latest state of the vendor sources in openpkg-src/xxx/xxx.spec. This
  -  especially means that unless openpkg-src/xxx/xxx.spec was upgraded, we do
  -  not upgrade (the version in) the openpkg-re/vcheck/vc.xxx - even if vcheck
  -  reports that a newer version exists. This way a "make report" always shows
  -  what still have to be done. Else we would get out of sync. Additionally the
  -  vc.xxx files do not carry any state except the latest version we packaged,
  -  i.e., the "lastcheck" and "errors" entries have to be removed before
  -  comitting a vc.xxx file. Additionally, make sure that in vc.xxx the "prog"
  -  entry either exactly reads "prog xxx" or at least starts with "prog xxx:",
  -  i.e., for reporting reasons all checked program URLs have the prefix of the
  -  package to which they correspond.
  +  This was the old version checking area of OpenPKG release engineering.
  +  It contained various vcheck(1) configurations (vc.*) which are now
  +  embedded in the package .spec files. Only a few legacy scripts are
  +  left here until they are replaced by the new tool chain.
   
  @@ .
  rm -f openpkg-re/vcheck/00TODO <<'@@ .'
  Index: openpkg-re/vcheck/00TODO
  ============================================================================
  [NO CHANGE SUMMARY BECAUSE FILE AS A WHOLE IS JUST REMOVED]
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to