[Svnmerge] Re: gnome stuck on cvs2svn

[Blair Zajac]

Giovanni Bajo wrote:
> Ben Collins-Sussman <sussman at red-bean.com> wrote:
> 
> 
>>The gnome project was supposed to migrate to subversion a month ago,
>>but have been stuck on a cvs2svn conversion problem:
>>
>>http://mail.gnome.org/archives/gnome-announce-list/2006-March/msg00025.html
> 
> 
> Marginally, I'll quote this:
> 
> ----------------------------------------------------------
> The second spanner is that container, our CVS (and to-be Subversion)
> server, is still running python2.2. Since I first started planning this
> migration (back in Aug/Sep), the cvs2svn code has moved on a fair bit,
> and includes some useful new features (e.g. storing the CVS version
> number for each revision as a subversion property). Unfortunately, it
> now requires python2.3, and I've been unsuccessful so far in getting a
> newer version of python working on container for various reasons
> (<cough>RHEL3</cough).
> ----------------------------------------------------------
> 
> I think it's a clear demonstration why client-side tools should try to be as
> compatible as possible with Python versions. svnmerge.py runs with any Python
> 2.0+ for a reason. It could be *marginally* cleaned up if the requisite was
> made higher, but to me it's really not worth the price to pay in compatibility.

If you're in the mood, contrib/server-side/svn-fast-backup could use a little 
backport effort :)

Just joking, but it uses subprocess which is distributed with Python 2.4 and all 
the RHEL3 and RHEL4 systems have older OSes.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
<blair at orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/