SVNUP-CVS(1) BSD Reference Manual SVNUP-CVS(1)NAMEsvnup-cvs - update a Subversion repository from a CVS repository
SYNOPSISsvnup-cvs repository path
DESCRIPTION
The svnup-cvs utility synchronizes a svn(1) repository with a cvs(1) one.
You should use this program if the CVS repository is here to stay (for
example, some project on which you work uses CVS), but you yourself want
to use Subversion for your daily tasks. Or you want to manage your own
branch of an upstream CVS repository in Subversion.
The synchronisation is done differently than in other programs of this
kind, notably cvs2svn(1) and svn_load_dirs(1). Not every single CVS revi-
sion is kept; instead, every svnup-cvs run imports the current revisions
in CVS into Subversion and tags the import with date and time (see
below). Additionally, all the CVS/ directories are preserved.
This has the following advantages:
- You can commit directly to CVS from inside a Subversion working copy.
Other solutions require you fiddling around with svn diff and manual
importing of the diff to CVS. This is tiresome.
- You do not always have to keep a "pristine" CVS working copy you up-
date from. Instead, you can delete everything under path to save disk
space.
However, there are also disadvantages:
- In the commit messages, the files under CVS/ generate some noise,
especially during updates.
- The Subversion repository grows much larger because of the overhead.
The arguments are as follows:
repository
The Subversion repository URL. For unattended runs, the reposito-
ry should be readable and writable without a password (e.g. using
a file:/// URL or a ssh key).
path The local path which is used during the update. This can be a
directory under /tmp, but using a persistent directory saves some
time, as the Subversion repository does not have to be checked
out each time svnup-cvs is run. This should really be an absolute
path.
EXAMPLES
To update a local "ports" repository, one could use the following command
line:
$ svnup-cvs file:///svn/ports $HOME/ports
SEE ALSOsvn(1), cvs(1)AUTHORS
This program was written for MirPorts by Benny Siegert <bsiegert@gmx.de>.
BUGS
Error handling (apart from abort-on-error) and parameter validation are
practically non-existent.
MirOS BSD #10-current September 20, 2004 1
