On Jun 21, 11:01 am, "Christian J. Robinson" <[email protected]> wrote: > On Tue, 21 Jun 2011, ZyX wrote: > > Reply to message �Re: Can not apply patch 7.3.202, 203, 223 cleanly�, > > sent 18:37:42 21 June 2011, Tuesday > > by Ben Fritz: > > > Why you can't just use mercurial repository? >
I do use the mercurial repository, but I expect that any method supported by Bram for getting the source ought to work, including patches as well as a-a-p and other less-used methods. > I can't speak for Ben, but for me it's because that would break the > self-contained source RPM package I roll for my CentOS machines. This > applies to virtually all RPM based Linux distributions, and > conceivably also Debian based, and other systems that use a similar > concept. > > While it's not /impossible/ to integrate mercurial into source RPM > build scripts, it is definitely considered a no-no. > > Not to be "snippy," but why put out patches in the first place if > they're just broken? > That's why I chimed in. I think either the patches should work, should have some instructions to make them work, or should not be made available. I'm surprised that google code doesn't seem to have a "download snapshot" feature like I've seen elsewhere (I don't remember whether it was github, bitbucket, or both), unless it's there and I've missed it. Is it too late to remove the runtime files from the patches? I understand that in versions < 7.3, runtime files were not included in the patches anyway, and that someone wanting to upgrade Vim would downloaded the runtime files separately...but it's been a long time since I did that. -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
