Philip Prindeville wrote: > I'm trying to automate building Vim from scratch, but I'm running afoul > of something. > > I start by grabbing and unpacking > ftp://ftp.vim.org/pub/vim/unix/vim-7.1.tar.bz2 and then grab > ftp://ftp.vim.org/pub/vim/unix/../patches/7.1/7.1.[0-9][0-9][0-9] ... > > Then I try to apply the patches as: > > patch -Np0 -d $vim_src_root < $patch > > in sorted numerical order. > > Seems to work fine until I hit patch 7.1.003, which applies the file > src/gui_w32.c ... which doesn't exist in the Unix tarball. > > What's the workaround?
The workaround I've been using is to get the full Unix+extra+lang sources: this eliminates rejects, unless there's a patch for a runtime file and you've been keeping the runtime files up-to-date separately (most of their changes are not refolected in the official patches). > > I could use -s -f to patch... but that's like driving without a > seat-belt. And even with -s, it's still really noisy. > > Plus do I want to have only part of a patch be applied? It seems to me > that patches should only be applied atomically (i.e. all files in the > patch, or none at all). > > What am I missing? > > -Philip If you keep your runtime files up-to-date separately (e.g. using rsync), as you should, there will occasionally be a patch for a runtime file for which you're using some newer version than what the patch expects as input, and the patch to that file will fail, but you can ignore it and keep the patches to other files in the same patch. I do the patching by hand when there are new patches, but patching errors to *.vim or *.txt files don't scare me, because I'll next (and periodically thereafter) be rsyncing my runtime files with Bram's, and even if I don't get the new version then and there (because the rsync server might not yet be updated) I'll eventually get it. For program source files (*.c, *.h, *.cpp, *.xs, *.pro, Makefile, configure.in, *.mk... are there others?) I download all three archives to start with, even though I'm running on Linux, because then there won't ever be patches to "missing sources"; and "unneeded sources" are not bothersome, they just won't be compiled when the time comes to run "make". To me, my peace of mind is worth downloading and updating the full set of sources, even those I eventually won't be compiling. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 213. Your kids start referring to you as "that guy in front of the monitor." --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
