You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ralf Schlatterbeck <rs...@runtux.com> on 2007/05/25 10:08:44 UTC
CVS pserver emulation for SVN?
Is there something that emulates the CVS pserver protocol on top of
subversion? I've googled for it but found nothing so far.
I'm involved in a project where the goal is a CVS to SVN migration for a
client. The current goal is a complete migration, not a cut-off where
some parts later live in an old CVS repo and the rest is converted to
SVN. We believe that having multiple sources of version-controlled
information is a path to madness :-)
We have identified the following obstacles:
- There are old build-scripts that rely on CVS. These live on old
branches in CVS. But it *could* occur that bug-fixes are necessary on
such an old branch. Rather than modifying the build-environment,
emulating cvs would be an easier solution.
- There are third-party tools in use that currently only support cvs.
So we are thinking about writing such an emulation if nothing exists.
Shouldn't be too complex if we're using subversions python interface?
But I can't believe nobody has thought about that before us...
Ralf
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting Fax: +43/2243/26465-23
Reichergasse 131 www: http://www.runtux.com
A-3411 Weidling email: office@runtux.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: CVS pserver emulation for SVN?
Posted by Erik Huelsmann <eh...@gmail.com>.
On 5/25/07, Ralf Schlatterbeck <rs...@runtux.com> wrote:
> Is there something that emulates the CVS pserver protocol on top of
> subversion? I've googled for it but found nothing so far.
>
> I'm involved in a project where the goal is a CVS to SVN migration for a
> client. The current goal is a complete migration, not a cut-off where
> some parts later live in an old CVS repo and the rest is converted to
> SVN. We believe that having multiple sources of version-controlled
> information is a path to madness :-)
> We have identified the following obstacles:
> - There are old build-scripts that rely on CVS. These live on old
> branches in CVS. But it *could* occur that bug-fixes are necessary on
> such an old branch. Rather than modifying the build-environment,
> emulating cvs would be an easier solution.
> - There are third-party tools in use that currently only support cvs.
>
> So we are thinking about writing such an emulation if nothing exists.
> Shouldn't be too complex if we're using subversions python interface?
It's not hard, but it's a lot of work. Do you intend to support
checkin too? That could be harder than you're estimating now.
Yes, others have thought about it (I), but since I have no need for it
myself, I have never persued the project any further.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: CVS pserver emulation for SVN?
Posted by Jeremy Wilkins <je...@ibexinternet.co.uk>.
Git has a well known pserver implementation, I'd guess this is in
either C or perl though. Bazaar NG also has one, written in python,
which might be a better starting point.
http://bazaar-vcs.org/BzrPlugins - under the Interop with other
version control section
bye
---
Jeremy Wilkins
Ibex Internet Ltd
Parkside Business Park
Parkside Rd.
Kendal
Cumbria
LA9 7EN
Tel: 0845 226 8342
Fax: 08718 729374
http://www.ibexinternet.co.uk/
On 25 May 2007, at 11:08, Ralf Schlatterbeck wrote:
> Is there something that emulates the CVS pserver protocol on top of
> subversion? I've googled for it but found nothing so far.
>
> I'm involved in a project where the goal is a CVS to SVN migration
> for a
> client. The current goal is a complete migration, not a cut-off where
> some parts later live in an old CVS repo and the rest is converted to
> SVN. We believe that having multiple sources of version-controlled
> information is a path to madness :-)
> We have identified the following obstacles:
> - There are old build-scripts that rely on CVS. These live on old
> branches in CVS. But it *could* occur that bug-fixes are
> necessary on
> such an old branch. Rather than modifying the build-environment,
> emulating cvs would be an easier solution.
> - There are third-party tools in use that currently only support cvs.
>
> So we are thinking about writing such an emulation if nothing exists.
> Shouldn't be too complex if we're using subversions python interface?
>
> But I can't believe nobody has thought about that before us...
>
> Ralf
> --
> Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
> Open Source Consulting Fax: +43/2243/26465-23
> Reichergasse 131 www: http://www.runtux.com
> A-3411 Weidling email: office@runtux.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org