Other Help Topics :: UCI question

Quote (lucky13 @ Jan. 29 2008,12:51)

Quote

Okay, so I'm guessing recompiling with --prefix=/opt/vim_7.1 will get all the paths into the /opt directory.

Yes, vim compiles very nicely there with no need for wrapper scripts. Are you going to add the patches (242 as of this moment)?

Sounds like you have it going already, so won't bother. Isn't the source getting updated with the patches?

Perhaps a vim update for the next release? Probably the help menu and spellcheck aren't needed (to cut down on size), but the visual features certainly are....Mikshaw's version would be a good model.

Quote

Isn't the source getting updated with the patches?

No, it's manual afaik. And from looking through the patch directory it looks like there can be over 500 between versions.

Quote (lucky13 @ Jan. 29 2008,14:43)

Quote

Isn't the source getting updated with the patches?

No, it's manual afaik. And from looking through the patch directory it looks like there can be over 500 between versions.

Sisyphus

I've never quite understood the process of applying multiple patches to the source. I've run a single patch occasionally, but the idea of running 500 seems to be a bit crazy. I assume that process can be automated?

Quote

I assume that process can be automated?

Of course. The recommended process at vim is to concatenate the patches into one patch and then apply it. Ports systems (such as in FreeBSD) run scripts to download source and patches, apply patches, then compile and install.

There are a couple other options for vim. The version in CVS is the patched version. So if anyone using CVS wants to build vim-7.1.uci, have at it. The other experimental option uses aap, which is similar to building ports. I want to look at this a little closer at this to see if it can be leveraged for compiling UCIs.
http://www.a-a-p.org/ports.html

Next Page...
original here.