On 18/07/09 17:26, Steve Hall wrote:
>
> On Sat, 2009-07-18 at 07:51 -0700, KF Leong wrote:
>>
>> The newest build (7.2.238) from Steve does not include updated
>> runtime files from the FTP, e.g. plugin/netrwPlugin.vim, version is
>> dated Aug 01, 2008, whereas on the FTP site, it is dated Aug 10,
>> 2008, and numerous others since updated.
>>
>> It is minor but ... :)
>
> The build script automatically builds from the default Vim .tbz, lang,
> and extra tarballs and then updates from the FTP site. (In case anyone
> is interested in the details, our build script is licensed under the
> GPL and available here:
> http://cream.cvs.sourceforge.net/viewvc/cream/misc/vim-build.bat )
>
> This process favors automation and repeatability, so there are no
> humans checking timestamps to verify version problems. Since our build
> machine was just re-built from scratch, it appears to me that there
> may be file date/version problems between the Vim sources and the FTP
> site. We've had problems with this before, particularly related to
> netrw, can any of the file/FTP site maintainers comment?
>
>
You're building using Cygwin, aren't you? Maybe you could keep your
runtimes up-to-date by rsync (if Cygwin has a version of that program)?
The script I use for that on Linux is
#!/bin/bash
date
rsync -avzcP --delete --exclude="/dos/" \
ftp.nluug.nl::Vim/runtime/ ./runtime/ 2>&1 | tee rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
(the last line because rsync uses CR without LF to overwrite its
"progress report" on the terminal). It is meant to be run after cd'ing
to the top vim72 directory, parent of runtime/ src/ etc. You may or may
not want to change some of the options.
Best regards,
Tony.
--
People will do tomorrow what they did today because that is what they
did yesterday.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
