Re: Moving bindings into a separate project.

Ben Reser wrote:

> So really that means we're down to perl, python and javahl bindings. We
> could probably easily release those as separate tarballs. We could have
> a directory in our repo for the shared files and use svn:externals to
> pull it in..

I'd really like to avoid svn:externals if possible...

Perhaps the swig files could exist in both the perl and python sections
of a repository, with changes merged between them when appropriate? Or
perhaps they don't really need to be shared at all. A lot of the
interesting parts of the swig files seems to be language specific
anyway. Do we gain all that much by sharing them?

-garrett

---------------------------------------------------------------------
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:48:29 2004