view release on metacpan or  search on metacpan

lib/App/SnerpVortex.pm  view on Meta::CPAN

actual repository use.  Tags that are modified later become branches.
Branches that are never touched are demoted to tags.

Snerp Vortex gains some benefits by doing tag and branch analysis
before converting the repository:

=over 4

=item *

Tag and branch analyses can be examined by a human without converting
the repository.  The L<snassign-gui> utility graphically browses the
repository structure over time.

=item *

Analysis errors can be fixed and redone quickly without waiting for
lengthy repository conversions each time.

=item *

Tagging and branching are performed as "git tag" and "git branch" at
appropriate times.  It's faster and smaller than duplicating directory
trees and converting them later.

=back

There is rudimentary support for multiple projects per repository, but
it needs love.

=head2 Toolset

Snerp Vortex is a chain of multiple tools.

=over 4

=item snanalyze

L<snanalyze> examines a Subversion dump and produces a SQLite database
that describes its structure over time.  snanalyze is intended to be
run first, as most other utilities require the SQLite database to
work.

=item snassign-auto

L<snassing-auto> attemtps to automaically assign tags and branches
based on directory locations and usage patterns.  It's generally run
after snanalyze and before snassign-gui.

=item snassign-gui

L<snassign-gui> is a Gtk2 utility to browse a repository analysis.
With it, one can page back and forth through significant revisions to
see how snassign-auto interpreted structural changes.

Some repositories will be too complex for snassign-auto to be
successful.  We hope a motivated individual will update snassign-gui
to be a tag/branch assignment editor so humans can override the
automatic assignment.

snassign-gui is intended to be used to verify that snassign-auto
worked correctly, before a possibly lengthy snerp run.

=item snerp

When everything is ready, snerp is called to export the Subversion
dump.  It takes as input the Subversion dump, and the index database
containing final tag and branch assignments.  It produces a new copy
of the repository in the desired format.

=back

=head2 Getting Subversion Dumps

Snerp Vortex requires a Subversion dump file, which is generally
created by running svnadmin dump on a local repository.

There's also a remote svn dump utility that may help, but we haven't
tried it: http://rsvndump.sourceforge.net/

=head2 Other Included Utilities

Snerp Vortex comes with some utilities and scripts that will
eventually be cleaned up and organized.  Until then:

=over 4

=item mkramdisk_osx

Create a 1 GB RAM disk with a case-sensitive filesystem.  Extremely
useful for Macintosh machines that use case-insensitive filesystems by
default.

=item snub

Snub the file contents of a dump.  Retains the file and directory
structure, but the resulting dump and replays are much smaller.
Written for Ævar Arnfjörð Bjarmason's six-gigabyte dump, which
triggers a hard to reproduce bug.

=item diff-test

Performs a recursive diff, excluding some things that Subversion may
have that another VCS may not.  For example, expanded "$Id$" tags.
Useful for testing the results of a replay, although it won't test
intermediate revisions... only the final ones.

=back

=head2 Development Scripts

Other development and/or test scripts are included in the distribution
but are neither installed nor documented here.  Browse around!

=head1 OSX Users

Get yourselves a case-sensitive filesystem.  This is easier done than
said.  Disk Utility can create empty random-access disk images with
the filesystems of your choice.  They mount in /Volumes and are
accessible like any other filesystem.