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

Re: Moving bindings into a separate project.

From: Dave Rolsky <autarch_at_urth.org>
Date: 2004-02-23 04:57:56 CET

On Sun, 22 Feb 2004 kfogel@collab.net wrote:

> I'll agree that decoupling and shipping separately *does* raise the
> bar to using the bindings, slightly. But how hard is it, really, to
> add a line to the release announcement for 1.1 saying that the
> bindings are now shipped separately, and telling people where to look
> for them? And for the recipients, is it *really* so hard to download
> and build another tarball for this functionality?
> Sure, it's a bit harder. But don't discount the current burden on
> developers. *All* users of Subversion, including those who never use
> bindings, are paying the price of that burden.

Actually, for Perl, in theory it can be easier. The vast majority of
bindings to C libraries are available from CPAN, and can be downloaded and
installed via the CPAN or CPANPLUS tools. Generally, the only
prerequisite is that you have the appropriate headers installed, which in
most cases will mean installing the appropriate libsvn-dev package for
your system.

AFAIC, having the Perl bindings only available in the core subversion
tarball is incredibly irritating, and makes installation much harder.


House Absolute Consulting

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 23 04:57:40 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.