Steve Hall wrote:
On Sat, 2007-03-17 at 22:45 +0100, A.J.Mechelynck wrote:
BTW, the sizes, datestamps, and versions I have are currently:

  18444  8-Jan 21:57 autoload/vimball.vim            version: 21
   5786  8-Jan 21:57 doc/pi_vimball.txt              2007-Jan-03
   1657  9-Oct 21:36 plugin/vimballPlugin.vim        (no version
mentioned)
190182  8-Jan 21:57 autoload/netrw.vim              version: 107
  10226  8-Jan 21:57 autoload/netrwFileHandlers.vim  version: 9
   7094  8-Jan 21:57 autoload/netrwSettings.vim      version: 9a "Jul
28, 2006"
  89232  8-Jan 21:57 doc/pi_netrw.txt                2007-Jan-03
   8528  8-Jan 21:57 plugin/netrwPlugin.vim          Jul 18, 2006

These are also the current versions on the rsync server. Steve, if
yours are older you sure may want to sync your runtimes.

Our installer uses runtimes current as of the build date. I don't have
access to the Windows build box ATM to double-check, but it would be
nice if third party plug-in authors would keep ftp.vim.org current.

They do. But some users omit deleting obsolete files no longer on server when they download the new versions. See further down.


Although (in my previous email) I understood that simply file-copying
a new version of vimball wouldn't necessarily fix my problem? Does it
actually have to be uninstalled, including it's preference file?



At one point (I'm not sure when) the netrw plugin was split to take advantage of the new "autoload" mechanism. The name of the global plugin was also changed from plugin/netrw.vim to plugin/netrwPlugin.vim. I haven't followed the vimball plugin as closely but (looking at the above) the case looks similar. If an old plugin (with the old name) was left behind beside the new one, you're in trouble.

Since you have cygwin on your build system (don't you?), maybe you could use a cygwin version of rsync to synchronise the runtime/ sibling of your src/ directory from the Vim server *with delete* to ensure that obsolete files are removed? Of course, I don't know how to set the nullsoft installer to check for "obsolete files which must be removed if present". Maybe any $VIMRUNTIME/*.vim not in the installer's embedded archive?

The command I use is:

rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/


Best regards,
Tony.
--
I get up each morning, gather my wits.
Pick up the paper, read the obits.
If I'm not there I know I'm not dead.
So I eat a good breakfast and go back to bed.

Oh, how do I know my youth is all spent?
My get-up-and-go has got-up-and-went.
But in spite of it all, I'm able to grin,
And think of the places my get-up has been.
                -- Pete Seeger

Reply via email to