Software Map

vss2svn is a Perl script (vss2svn.pl) and accompanying C program (ssphys.exe) to migrate revision history from a Microsoft Visual SourceSafe (VSS) database to a Subversion repository. This combination of programs was designed by reverse-engineering the backend database structure of Microsoft's VSS repository. In doing so, the authors have made progress towards overcoming the inability of even Microsoft's own API to properly recover deep history from VSS. This also means that you don't actually need a copy of VSS or its libraries to convert your repository.

SvnHg is a command-line tool to convert from a Subversion repository to a Mercurial one, preserving the whole history of the repository.

svngroup is a collection of tools designed to
facilitate advanced access control lists for
Subversion repositories. Unlike tools such as
svnperms.py or authz, svngroup puts the
manipulation of ACLs directly in the hands of
group owners. Group owners are those individuals
who have been granted "special" privileges in the
repository and can make decisions regarding who
can and can't submit to a particular location in
the repository.

Marsh is an interactive command line utility for
browsing and manipulating a Subversion repository.
A cross between tools like ViewVC and lftp, Marsh
makes it easy to locate and check out a subproject
or perform complex server-side changes. Users of
the Subversion command line tool can move
immediately to Marsh due to the common command
set.

Ksvn is an SVN client for KDE that looks like
tortoiseSVN. It can be used from the Konqueror
context menu and replaces the standard KDE
SubVersion menu. You can directly add, revert, and
delete files from the commit dialog with a file's
context menu.

BundleMan manages the releases of an application built on versioned products under Subversion. An application is seen as a product suite defined using the Subversion svn:externals property. An application is a bundle of products. Products are versioned pieces of software. Releasing an application is about taking care of tagging the source repository, managing the version of each products, managing CHANGELOGs, creating a source package archive, and giving ways to maintain a release without blocking the trunk development.