Saluton Ryan :) Ryan J M <[email protected]> dixit: > I have been a vimmer for years, but it was my first time to build it > from src, because I found that my CENTOS vim got some problems on > cscope co-operations. > Following README file lcoated at > ftp://ftp.vim.org/pub/vim/patches/7.2/README, I got a little pain when > patching. please take a look at logs at the bottom.
Probably your problem is that your vim72 sources doesn't include the "extra" files? If you are going to use all the patches published by Bram you need to have the pristine sources and the extra sources. This is a blind shot because I haven't had time to read your problem. I've patched my Vim to 228 (by now...) without any problem, and I do it automatically using a little shell script. > why don't vim provide a whole big patch for 001-latest one? Bram already provides 001-100, 100-200, etc. Providing 001-latest would be a bit of a problem due to the following reasons: - Bram would have to work a bit more each time he writes a patch. He is not paid for his work on Vim, and even if he is, this is additional and unneeded work. Instead of uploading the new patches, he would have to make sure to update the 001-latest tarball (or whatever) with each patch. I wouldn't do it, for sure. And I prefer Bram working in Vim rather than doing administrative tasks. - People like me, who automates the process, can now download only the new files (new patches, etc.) using wget instead of downloading a big tarball each time. This would be slower and less comfortable. For a start, I can tell if new patches have been published just by looking at the directory listing at ftp.vim.org (although I don't do it, I'm subscribed to vim_dev instead). - Some other very intelligent reason that I can't think about right now because I'm not clever enough ;) For me, saving time for Bram is enough. > patching file runtime/doc/os_vms.txt > can't find file to patch at input line 743 > Perhaps you used the wrong -p or --strip option? Don't know the rest of the problems, this one is caused by not having the "extra" sources. You have only the UNIX sources, download the file "vim-7.2-extra.tar.gz" and the patches should apply cleanly. I usually download "vim-7.2-lang.tar.gz" too, just in case. Having the full sources is better if you patch frequently: you don't have to cherrypick the patches, then. -- Raúl "DervishD" Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
