Steve Hall wrote:
From: "A.J.Mechelynck", Jun 6, 2006 9:30 AM
Until or unless....I think I'll take a back seat to the development
of Vim executables for Windows.
Tony, for what it's worth, I've improved the Cream build routines so
that we can stay on top of patches more easily. Our previous delay was
due to a hardware changeover that is now in the past, and we can now
do the whole patch/build with a single command. Once we script the
upload and page reference updates, the whole thing will be croned
nightly.
Good! So I really can afford to leave the distribution of W32 Vim safely
in your hands.
I'd do the same with GNU/Linux, but I haven't figured RPMS yet. :)
And even if someday you do understand RPM (used by RedHat and SuSE),
you'll still have to figure out dpkg (for Debian) and what-not... I have
compiled gvim on my SuSE system and found the process remarkably easy.
If you have comments about my new HowTo for Linux (
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm ) I sure want
to hear them. For one thing, you will notice that contrary to "official"
recommendations, I don't modify the Makefile: so I keep track of my
configure options for use with the next version; and if a patch someday
affects the Makefile it won't be thrown out of sync because of anything
I did.
I don't have Python in my current gvim but I can live without it; there
is a python-devel package in my distribution but it refuses to install
(bad RPM format or something). I may someday look into it but it's low
on my agenda.
Oh, and BTW, the version of Vim that came with that SuSE distribution is
a kvim 6.2.014. How old is that? I used it for one day to make ready to
compile my own, and now I don't need it anymore. Good riddance!
Best wishes to you. :-)
Best regards,
Tony.
