Arch Linux

I made a commitment to not having Ruby in vim packages until it is officially supported. I know there are multiple patches out thre trying to bind the new Ruby to vim and there are reports for most of them with things not working accordingly. The problem here is that not all available rubyscripts will work with 1.9 and people will blame that at vim. I'll wait for the vim people to make a move

Fair enough. Time to go harass the Vim guys then...

As of Patch 7.2.368, the Ruby interface for Vim has been updated to
work with Ruby 1.9:

http://osdir.com/ml/general/2010-02/msg21930.html

It would be nice to have --enable-rubyinterp turned back on.

Thanks,
Michael Henry

ruby should be readded to the depends array and the package needs to be built with ruby being present

Hmm... Doesn't currently build with ruby enabled

Ya, Dan, you can close this. Until Gvim builds out of the box with ruby nothing should be doen. All the patches I saw online seem sketchy. I don't think gvim will jump on that wagon until Ruby2.0 hits the shelf. If there are any patches for it I think AUR shall iron that out first. If we introduce that to extra there is a lot of trouble ahead.

Hi,

I think the reason you're having trouble building with Ruby support is because your ``get_patches()`` function in ``fetch_patches.sh`` was changed, and none of the patches are applying correctly. The patching is being done in ``src``, but it should be done in ``src/vim72``.

Attached is a patch for fetch_patches.sh which uses the ``-d`` option of ``patch`` to change to ``${_versiondir}`` such that the patches apply correctly. Included in the patch is a replacement ``rsync`` invocation because for some reason on my box, the flurry of ``wget`` invocations fail for a couple of dozen patches. If ``rsync`` is an acceptable build-time dependency, it would speed up the fetching of patches and make it more reliable (as it would the fetching of the runtime files). But of course, that's a separate concern. In addition, the patch uses ``>>`` instead of ``>`` to redirect the patching error messages; otherwise, only the last patch's output ends up in ``vim.full.patch.log``. Failing patches previously didn't fail the ``get_patches()`` function, so I've added ``|| return 1`` to the ``patch`` invocation as well.

--- fetch_patches.sh (revision 69676)
+++ fetch_patches.sh (working copy)
@@ -7,12 +7,11 @@
let _patchlevel=$_patchlevel+1
_currpatch=$(cat MD5SUMS | wc -l)
sed -i "${_patchlevel},\$d" MD5SUMS
- cat MD5SUMS | awk '{ print $2 }' | sed -e \
- "s|^|ftp://ftp.vim.org/pub/vim/patches/${_srcver}/|" | \
- xargs -P 0 -r -n 1 wget -nv
+ rsync -avzcP "ftp.nluug.nl::Vim/patches/${_srcver}/${_srcver}.*" .
md5sum -c MD5SUMS > /dev/null || return 1
+ > vim.full.patch.log
for file in $(cat MD5SUMS | awk '{ print $2 }')
- do patch -p0 < $file > vim.full.patch.log; done
+ do patch -d ${_versiondir} -p0 < $file >> vim.full.patch.log || return 1; done

########


I'm not sure how mangled this patch will become, but hopefully the verbiage above explains the problem well enough. With the above patch, I can successfully build using -r69676 of the vim package. I've not tried the gvim package yet, but using my own build scripts, I'm able to build a ``huge`` version of Vim which works with the Ruby integration and which includes X support (and basically everything).