John Beckett wrote: > Ben Schmidt wrote: >> I gave up on SVN ages ago--I would have loved to use it, but >> it's just too messy. Now I apply patches. Below is the script > > Eventually I'd like to have a tip (http://vim.wikia.com/) on building Vim, > with > probably one overview article, and separate articles for downloading, > patching, > configuring, building, installing (and possibly separate pages for different > platforms). > > Like you, I decided to do my own "get patches" script. In my case, a command > like > 'getpatch.py 1 18' will download patches 1..18 into a single file named > 'patch-7.2.001-018'. > > Any thoughts? Should I put your script and my script on a page as a > starting point?
Might as well. It's easier to delete stuff than recreate it. I think in the end we'll want something simple that will work on as many systems as possible (which I think probably means using shell script and standard utilities without GNU extensions to cover Unix and Mac, and some batch script for Windows if it's even possible without extra software on that OS...). Perhaps an alternative would be suggesting and creating a make target that could handle the downloading and patching (again, in a very platform-independent way) and ask Bram to consider it. If Vim building could be ./configure; make patch; make; make install or something like that, it could be nice and accessible. Another issue that should be included is keeping runtime files up-to-date. Another make target? A vim plugin that calls the shell to do it? I don't know. But that's another thing worthy of a tip. Ben. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
