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

Re: Diff lib

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-01-10 00:17:39 CET

On Thu, Jan 09, 2003 at 06:28:05PM +0100, Daniel Stenberg wrote:
> On Thu, 9 Jan 2003 rbb@rkbloom.net wrote:
> > I'll take a look at the C framework, and see if I can just use it. The
> > other option is to actually split the diff library out and make it a
> > separate project. Then another testing framework wouldn't be a big deal.
> > ;-)
> IMHO, I think the diff library would benefit from getting separated from
> Subversion and put in its own little project.
> Then it'll be easier for non-Subversion people too to join in that work etc.

We've generally had a policy that provides a *much* lower bar for committers
who are restricted to particular areas of code. Thus, it would be quite easy
to add committers who are specifically working on the difflib.

But that said, I'm a big +1 for separating the library when the time is
right. I think it will easiest to get the code done and working for
Subversion while it is sitting in the SVN tree. *After* that, we can do:

$ svn mkdir http://svn.collab.net/repos/svn/projects
$ svn co http://svn.collab.net/repos/svn/projects
$ svn mkdir projects/difflib projects/difflib/src
$ svn mv trunk/subversion/libsvn_delta/diff.c projects/difflib/src

If we separated now, then we'd have to get some config/build logic around
the difflib, and then change SVN to find and use it, and ...

Oh, and I'm also +1 if Ryan chooses to switch SVN over to CuTest. We don't
have much invested in the C-based framework, so switching to something a bit
more "standard" is fine with me.

(but I'm -0.5 on such a move for our Python framework right now)


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 10 00:16:30 2003

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.