On 23/11/09 16:23, Raúl Núñez de Arenas Coronado wrote:
> Saluton Mr.SpOOn :)
> Mr.SpOOn<[email protected]> skribis:
[...]
>> Well, there are archives to download them easier, so that would not be
>> a problem. The problem would be to patch them all. I shall write a
>> script for that. I was just wondering if I had to download all of
>> them.
>
> rsync will download only new patches (see Tony's instructions for that),
> and after that I recommend that you ALWAYS build from pristine sources.
> That is, extract the tarballs and apply ALL patches again. This is fast
> and saves you from having to track which patches you already applied.
> And if you, like me, like to build different versions at times, tweaking
> the sources, etc. it's better to build from scratch, just in case.
>
AFAIK (but maybe there is something I didn't realize), rsync is for the
runtimes, not the patches. However, unlike Raúl, I prefer the
"incremental" build philosophy here. At the moment my source is patched
to patchlevel 7.2.315, which is the latest "official" patchlevel. Let's
imagine that next week Bram publishes ten patches within a few hours of
each other. I will then notice them on the vim_dev list, download
7.2.316 to 7.2.325 from the FTP server, and use the patch utility to
apply only these ten patches, in ascending numeric sequence. Then I will
run "make 2>&1 |tee make.log". Probably everything will run OK, but if
make tries to run configure it will probably complain about
auto/config.cache, telling me to remove it. In that case I'll do that
(but only in that case, because removing that file _forces_ make to run
configure, which can be quite long, then recompile everything, which is
also quite long -- quite longer at least than recompiling only what has
changed) and restart the make.
Best regards,
Tony.
--
Q: How many Oregonians does it take to screw in a light bulb?
A: Three. One to screw in the lightbulb and two to fend off all those
Californians trying to share the experience.
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
