Re: Moving bindings into a separate project.

[This is co-written with Mike Pilato.]

Well, sometimes the most important thing is to know when to lose an
argument :-).

It's clear that many developers -- more than we expected -- want to
keep the bindings in the tree and distribute them with Subversion, and
that in general more people want the trend to be toward tighter
integration than looser.

So, let's leave them in and try to clean up any problems they still
have. Theoretically, now that the Subversion API is stabilized,
bindings development will be a lot easier. If they do turn out to
interfere with core (by which we mean the C libraries) development,
then we can revisit this issue -- and you know we will :-).

I think we did have general agreement that distribution and
development are tied together (or did someone disagree with my
assertion that they are?). That is, if the bindings ship with
Subversion, they should live in the Subversion repository; if they
ship separately, they should have their own repository. The consensus
right now seems to be for the former, so they stay in.

We'll send a separate mail about specific procedures for making
in-tree bindings development easier in the future.

-Mike & Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 24 22:06:03 2004