[ANNOUNCE] RSVN - Remote Subversion 0.1

[François Beausoleil <fb...@ftml.net>]

Announcing release 0.1 of RSVN - a Python script to execute multiple
commands on a repository, without a working copy.

The problem
===========
Copying and moving huge amounts of data is a pita with a working copy.
All paths need to be locked and unlocked on every svn subcommand.

The solution
============
Execute the commands server-side (or at least, repository-side in this 
version).

What can it do ?
================
rmkdir, rcopy and rdelete (which implies rmove also exists).

What's missing ?
====================
Automated tests (unit and functional)
Commands:  redit, rpropset, rpropdel, rmerge, radd, rmove (rcopy + rdelete).
Shell access to the repository:  begin, commit, rollback, ls, cd.

Warnings and caveats
====================
MAKE A BACKUP OF YOUR REPOSITORY !
This is critical, as this script has received minimal testing.  It does
what I need, no more, no less.

Make sure that the target of your copy is named *explicitely*.  The
following won't work:
   rmkdir vendor/libcalc/releases
   rcopy vendor/libcalc/0.1 vendor/libcalc/releases

Instead, do the following:
   rmkdir vendor/libcalc/releases
   rcopy vendor/libcalc/0.1 vendor/libcalc/releases/0.1

If you do the former, you will end up replacing releases with a copy of
libcalc/0.1, which is not the intended results.

The implementation
==================
rsvn.py
   http://opensvn.csie.org/rsvn/tags/0.1/

Wiki available at:
   https://opensvn.csie.org/traccgi/rsvn/trac.cgi/wiki

Enjoy !
François Beausoleil

Re: [ANNOUNCE] RSVN - Remote Subversion 0.1

[kf...@collab.net]

François Beausoleil <fb...@ftml.net> writes:
> Announcing release 0.1 of RSVN - a Python script to execute multiple
> commands on a repository, without a working copy.

Is the important thing about this script that it allows you to do
multiple operations in a single (atomic) commit, without a working
copy?

If so, you might want to say that up front... :-)

-Karl

> The problem
> ===========
> Copying and moving huge amounts of data is a pita with a working copy.
> All paths need to be locked and unlocked on every svn subcommand.
> 
> The solution
> ============
> Execute the commands server-side (or at least, repository-side in this
> version).
> 
> What can it do ?
> ================
> rmkdir, rcopy and rdelete (which implies rmove also exists).
> 
> What's missing ?
> ====================
> Automated tests (unit and functional)
> Commands:  redit, rpropset, rpropdel, rmerge, radd, rmove (rcopy + rdelete).
> Shell access to the repository:  begin, commit, rollback, ls, cd.
> 
> Warnings and caveats
> ====================
> MAKE A BACKUP OF YOUR REPOSITORY !
> This is critical, as this script has received minimal testing.  It does
> what I need, no more, no less.
> 
> Make sure that the target of your copy is named *explicitely*.  The
> following won't work:
>    rmkdir vendor/libcalc/releases
>    rcopy vendor/libcalc/0.1 vendor/libcalc/releases
> 
> Instead, do the following:
>    rmkdir vendor/libcalc/releases
>    rcopy vendor/libcalc/0.1 vendor/libcalc/releases/0.1
> 
> If you do the former, you will end up replacing releases with a copy of
> libcalc/0.1, which is not the intended results.
> 
> The implementation
> ==================
> rsvn.py
>    http://opensvn.csie.org/rsvn/tags/0.1/
> 
> Wiki available at:
>    https://opensvn.csie.org/traccgi/rsvn/trac.cgi/wiki
> 
> Enjoy !
> François Beausoleil
> 
> 
> ---------------------------------------------------------------------
> 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