Path::Dispatcher: a dispatcher that can work just about anywhere. It works (roughly) analogously to the way mod_perl works when matching URIs and dispatching to URI handlers. This code can work in any context including the command line.

IPC::Run3: the successor to IPC::Open2. A simpler API with the same functionality.

Ever wondered about Perl modules that would help you build a dependency tree in a manner similar to make? A recent PerlMonks question was also curious. Only one answer (so far) but the question plus the answer have some interesting ideas.

The answer suggested cons. cons is a very old system and I had not realized it was still active...and based on the e-mail archive, it isn't. The FAQ was last updated in 2001. This would not likely be the first place I would look.

The question itself mentioned two modules that I was unaware of: Algorithm::Dependency and Decision::Depends. The former appears to be the module with the most recent update, but the OP seems to have chosen the latter to help him solve his problem.

Config::Model: A framework for creating configuration validation and editors. This is something I've wanted to write for awhile now. If I understand the goal of this module correctly it should make writing configuration systems very simple.

App::perlbrew: Manage perl installations in your $HOME. I can see where this can be very useful. Here is an introduction on its use.

Moose: It looks like version 1.0 of Moose has finally been released. I don't use Moose and my initial introduction to Moose (over 1.5 years ago now) was not a particularly positive experience. Having said that I would say that this is a pretty big deal. It seems a lot of people really like Moose and I think that sometime in the near future I may jump on the Moose bandwagon.

Acme::Module::Build::Tiny: A tiny replacement for Module::Build. Written by the same author who maintains Module::Build. It is missing a lot of features, but if you don't need those features this module is very light.

Scope::OnExit: Execute code on scope exit. I'm not certain when I'd use this, but it looks useful for theoretically interesting things.

SQL::Statement: SQL parsing and processing engine. The documentation details three things the author believes this module is good for.

PAR: The Perl Archive Toolkit. Perl's answer to tools such as jar. Allows the user to package up a complete distribution, including all dependencies, into a single file. Very, very cool.

PAR::Packer: A companion to the above module. This is a frontend script that allows for (among other things) the creation of standalone executable files that contain an entire distribution (including perl itself!).

NEXT: I don't know that I will ever use this module, but it is interesting. Provides for interesting method dispatching scenarios such as calling all DESTROY's in the inheritance tree.

Net::Amazon::EC2: Perl interface to the Elastic Compute Cloud (EC2) environment. I'm not certain if this is a competitor to the Amazon Perl API or if it somehow complements it.

XML::Compile::SOAP: A real replacement for SOAP::Lite.

POE::Filter::HTTPD::Chunked: As a big proponent of POE I thought this looked interesting. A drop-in replacement for POE::Filter::HTTPD that can deal properly with chunked encoding.

Template::ShowStartStop: Inserts comments in the generated output to show where one template ended and a new one begins. It overrides Template Toolkit's Template::Context to do this.

UNIVERSAL::require: A module that gets around the silly bareword requirements for the builtin require() sub.

IPC::Cmd: An API to run external commands. A wrapper around system() I would guess, but very nice looking.

SQL::Translator: Translate the DDL from one schema type (say, Oracle) to another (say, PostgreSQL). It can also be used to translate a schema to something completely different, such as a YAML file. One particularly nice feature is the ability to translate a schema to code. An example of this would be translating a MySQL schema to Class::DBI code. Introductory documentation is available.

Sub::Override: Instead of writing this:

  undef (local *Some::sub);
  local *Some::sub = sub { ... };

You would write:

  Sub::Override->new('Some::sub', sub { ... });

The scoping rules are (mostly) the same and it is more readable. Very useful for tests.

Data::Random: Generate random words, characters, numbers, date, time, .... Seems like this would be very useful for testing.

Fey::ORM::Mock: An attempt at a replacement for DBD::Mock. The author suggests it is better but does not eliminate all the problems with DBD::Mock. Likely requires that you use Fey::ORM as your object to relational mapper.