Re: Testsuite broken by svntest changes in svn trunk

On 17/06/10 08:05, Michael Haggerty wrote:
> I work with git-svn and rarely update the svn:external.

Heh. And I work with bzr-svn and also need to manually update the
external :-)

>> I think we should do one of two things:
>>
>> EITHER: Use a pinned revision in the svn:externals.
>>
>> OR: Embed svntest into our tree.
>>
>> I've never liked the idea of svn:externals much, so I favour the second, 
>> but I could be persuaded to the first.
> 
> Either solution is OK with me.  If you choose the latter, then it would
> be great if you would set up an update.sh script like the one in
> cvs2svn_rcsparse.

Given it turns out that neither of us are using a client that handles
svn:externals, the choice is clear :-)

> And I suppose we should decide on a policy--are we
> forking svntest (basically sticking to the current version and adding
> our own modifications) or are we going to try to track upstream svntest,
> just at our own pace?  I think the latter is more realistic, given our
> limited resources.

Agreed.

> I've also been wondering how much we really use from svntest, and
> whether the Subversion-specific stuff there is rather holding us back.
> Maybe with time we should migrate more towards python's unittest module,
> using the stuff in svntest only for parsing SVN output etc.

That sounds sensible to me.

Max.

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2623401

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkwbPtIACgkQfFNSmcDyxYBXkgCfYapvqScd+cE2JYXgBIs8RZUw
POcAoL1h0l3yXF+Icds3M8IimhGwjOF1
=kc5e
-----END PGP SIGNATURE-----