[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: <kfogel_at_collab.net>
Date: 2004-02-20 19:10:02 CET

Garrett Rooney <rooneg@electricjellyfish.net> writes:
> +1 on moving them 'somewhere', but i'm curious exactly how this should
> be handled. Several of the bindings depend on the same files (swig
> stuff), but could easily be released separatly. Would we really want
> a single subversion-bindings-1.0.x.tar.gz, or would it make more sense
> to have subversion-perl-1.0.x.tar.gz, subversion-python-1.0.x.tag.gz,
> subversion-java-1.0.x.tar.gz, etc. If that does make more sense, how
> do we handle the files that are shared between various bindings?

I don't know; this is something for the bindings maintainers to work
out (and, it makes me realize that at least a dedicated dev@ list for
the bindings will probably be necessary.)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 20 20:12:39 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.