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:   04-Oct-2006 07:45:53
  Branch: HEAD                             Handle: 2006100406455200

  Modified files:
    openpkg-src/vim         vim.spec

  Log:
    upgrading package: vim 7.0.116 -> 7.0.118

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

  patch -p0 <<'@@ .'
  Index: openpkg-src/vim/vim.spec
  ============================================================================
  $ cvs diff -u -r1.433 -r1.434 vim.spec
  --- openpkg-src/vim/vim.spec  3 Oct 2006 17:47:23 -0000       1.433
  +++ openpkg-src/vim/vim.spec  4 Oct 2006 05:45:52 -0000       1.434
  @@ -25,7 +25,7 @@
   #   package versions
   %define       V_vl  7.0
   %define       V_vs  70
  -%define       V_pl  116
  +%define       V_pl  118
   
   #   package information
   Name:         vim
  @@ -38,7 +38,7 @@
   Group:        Editor
   License:      Charityware
   Version:      %{V_vl}.%{V_pl}
  -Release:      20061003
  +Release:      20061004
   
   #   package options
   %option       with_x11        no
  @@ -169,6 +169,8 @@
   Patch114:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.114
   Patch115:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.115
   Patch116:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.116
  +Patch117:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.117
  +Patch118:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.118
   
   #   build information
   Prefix:       %{l_prefix}
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to