[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [RFC] Streamlining Binding Installation

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-09-02 22:12:35 CEST

--On Thursday, September 2, 2004 4:00 PM -0400 David James <staple@gmail.com>

> Here's a condensed version of my original proposal:
> 1. By default, don't install any bindings (because not everyone has
> Java, Python, or Perl)
> 2. If they ask to install the bindings (in the configure script), then
> build and install them with the rest of subversion!

If SWIG supports the language, we'll automatically enable the bindings for
that language. So, lots of people will get these options enabled without
asking first. (Yes, we could change that, but I don't think we should.)

Part of the problem is that the bindings don't build everywhere just yet.

As I mentioned before, Perl doesn't work for me at all. And, since they don't
use the standard build system, I can't do much to help as they use some goofy
Perl-only build system that is rather buggy (ExtMaker or something).

JavaHL is only beginning to get wide enough usage (outside of me and Patrick)
to where we're getting useful feedback on the build system. It's probably
close enough to turn it on for everyone if we detect the right tools.

By and large (I'm not sure what C-Mike is seeing), the Python builds are going
to be the best supported because they've been in the tree the longest.

I'm not against it, but turning on an option when we know some don't build and
only one or two people know how to fix it isn't goodness. My hunch is the
1.2.0 release (i.e. our next major release) can have this on by default. We
can shoot for having the build kinks worked out by then. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 2 22:12:51 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.