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

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   15-Jun-2005 19:38:50
  Branch: HEAD                             Handle: 2005061518385000

  Modified files:
    openpkg-src/vim         vim.spec

  Log:
    upgrading package: vim 6.3.76 -> 6.3.78

  Summary:
    Revision    Changes     Path
    1.380       +4  -2      openpkg-src/vim/vim.spec
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-src/vim/vim.spec
  ============================================================================
  $ cvs diff -u -r1.379 -r1.380 vim.spec
  --- openpkg-src/vim/vim.spec  8 Jun 2005 18:41:44 -0000       1.379
  +++ openpkg-src/vim/vim.spec  15 Jun 2005 17:38:50 -0000      1.380
  @@ -25,7 +25,7 @@
   #   package versions
   %define       V_vl  6.3
   %define       V_vs  63
  -%define       V_pl  76
  +%define       V_pl  78
   
   #   package information
   Name:         vim
  @@ -38,7 +38,7 @@
   Group:        Editor
   License:      Charityware
   Version:      %{V_vl}.%{V_pl}
  -Release:      20050608
  +Release:      20050615
   
   #   package options
   %option       with_x11        no
  @@ -132,6 +132,8 @@
   Patch74:      ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.074
   Patch75:      ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.075
   Patch76:      ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.076
  +Patch77:      ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.077
  +Patch78:      ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.078
   
   #   build information
   Prefix:       %{l_prefix}
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to