Sometimes you want roles. You're not sure about Moose, Mouse, Moo and
what was that damned Squirrel thing anyway? Then there's Class::Trait,
but it has a funky syntax and the maintainer's deprecated it in favor
of Moose::Role and you really don't care that it handles overloading,
instance application or has a workaround for the SUPER:: bug. You
think a meta-object protocol sounds nifty, but you don't understand
it. Maybe you're not sure you want the syntactic sugar for object
declaration. Maybe you've convinced your colleagues that roles are a
good idea but they're leery of dragging in Moose (your author has had
this happen more than once and heard of others making the same
complaint). Sometimes you just want good old-fashioned roles which let
you separate class responsibility from code reuse.
SVN::Access includes both an object oriented interface for manipulating
SVN access files (AuthzSVNAccessFile files), as well as a command
line interface to that object oriented programming interface
(svnaclmgr.pl) which is in the examples/ directory.
This module mirrors remote repositories to a local Subversion
repository. It supports remote Subversion repositories accessible
via the SVN::Ra interface; other version control systems (such as
Perforce and CVS) are also supported via the VCP module.
S4 provides a wrapper to subversion that extends several of the commands
(for example, "fixprop", "scrub", "snapshot"). It understands all svn
commands; you may simply use "s4" wherever you would normally type
"svn".
Set::Tiny is a thin wrapper around regular Perl hashes to perform
often needed set operations, such as testing two sets of strings for
equality, or checking whether one is contained within the other.
String::Formatter is a tool for building sprintf-like formatting
routines. It supports named or positional formatting, custom
conversions, fixed string interpolation, and simple width-matching out
of the box.
Term::RawInput is a simple drop-in replacement for <STDIN> in scripts
with the additional ability to capture and return the non-standard keys
like 'End', 'Escape', 'Insert', etc.
This is another framework for writing test scripts. It is loosely
inspired by Test::More, and has most of its functionality, but it
is not a drop-in replacement.
This module allows you to specify the number of expected tests at
a finer level of granularity than an entire test script. It is built
with Test::Builder and plays happily with Test::More and friends.
The Test::Cmd module provides a low-level framework for portable automated
testing of executable commands and scripts (in any language, not just Perl),
especially commands and scripts that interact with the file system.