Re: [PATCH] build/win32/make_dist.sh supports the Ruby bindings

Hi,

In <ae6cb1100703170942t57d3e51bvec0d69eacd26f7ba@mail.gmail.com>
  "Re: [PATCH] build/win32/make_dist.sh supports the Ruby bindings" on Sat, 17 Mar 2007 09:42:50 -0700,
  "Joe Swatosh" <joe.swatosh@gmail.com> wrote:

> > > ===================================================================
> > > --- build/win32/make_dist.py (revision 23865)
> > > +++ build/win32/make_dist.py (working copy)
> > > @@ -260,6 +260,21 @@
> > > '%(bindsrc)s/java/javahl/classes'),
> > > ),
> > >
> > > + 'ruby': None,
> > > + 'ruby/lib': None,
> > > + 'ruby/lib/svn': FileGlob('%(bindsrc)s/swig/ruby/svn/*.rb'),
>
>
> These three lines deleted:
> > > + 'ruby/ext': None,
> > > + 'ruby/ext/svn': None,
> > > + 'ruby/ext/svn/ext':
>
> And the ext directory living right under svn:
> 'ruby/lib/svn/ext':

Normally, extension libraries are installed into
.../site_ruby/VERSION/ARCHITECTURE/ and ruby scripts are
installed into .../site_ruby/VERSION/.

For example:
  VERSION: 1.8
  ARCHITECTURE: i386-msvcrt

In my plan, user installs the Ruby bindings like the
following:

  * Copies ruby/lib/* into .../site_ruby/1.8/
  * Copies ruby/ext/* into .../site_ruby/1.8/i386-msvcrt/

> Plus the .rb files to dink the windows path for thr process and
> require the corresponding dll directly.

It's not needed. I already put the mechanism into svn/util.rb.

Thanks,

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org