As of SVN 1.2.0 there are ruby bindings in the svn trunk. In the current 1.2.1 ebuild, there's support for java, python and perl. It would be great if someone could add in the ruby support to the ebuild. Reproducible: Always Steps to Reproduce: 1. emerge subversion 1.2.1 with 'ruby' as a use flag 2. 3. Actual Results: no ruby bindings installed Expected Results: ruby bindings installed
Created attachment 71110 [details, diff] Patch to subversion-1.2.3-r3.ebuild to add ruby bindings
This patch modifies the subversion ebuild to compile and install the Ruby bindings if the user has USE=ruby. I got the required swing version wrong in the patch. Will fix this now.
Created attachment 71118 [details, diff] Patch to subversion-1.2.3-r3.ebuild to add ruby bindings
Created attachment 71119 [details, diff] subversion-swig.m4-ruby.patch
I've just committed a new version of -r3 (as having most users who don't need ruby bindings recompile would be kindof pointless).
Currently the -r3 ebuild (1.3 2005/10/24 14:35:26 pauldv) causes subversion compilation to fail with USE="ruby" giving: /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool: line 1238: none: command not found make: *** [subversion/bindings/swig/ruby/svn_client.lo] Error 1 Looking at the ebuild, the swig version required is still 1.3.21, not .35 as in the lastest patch, so perhaps your changes haven't propagated or didn't take. (or the wrong patch was applied...) It's been about 12 hours since the commit reported in comment #5, so I'm reporting this. I'll wait and resync later, but it should be checked.
Please attach the 20 lines of output before "none: command not found".
I've just fixed the depend, but I suspect the none coming from an improperly configured jdk (java-config then reports none instead of the location of javac)
