Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Log message:
Update p5-Path-Dispatcher to 1.04.

Changes from previous:
1.04 Thu Sep 1 2011
        Explicitly depend on Test::Fatal (reported by Jérôme Quelin  \ 
[rt.cpan.org #70666])
        Convert all tests from Test::Exception to Test::Fatal

1.03 Tue Aug 30 2011
        Provisional support for arbitrary payloads, not just code blocks, as results
            See https://github.com/sartak/path-dispatcher/blob/master/t/200-payload.t
        Eventually blocks will be deprecated, but not for a while. Internally \ 
blocks are
        rewritten as payloads so if you're doing deep magic with PD you may be \ 
exposed to
        that implementation detail.

1.02 Tue Nov 2 2010
        Various improvements to the handling of $match->leftover with undef

1.01 Sun Oct 24 2010
        Skip t/026-named-captures.t if you don't have 5.10.1

        Give matches a ->parent for inspecting an Under prefix rule's
            captures etc

1.00 Sun Oct 17 2010
        Bump to 1.0 to indicate back compat breakage

        Add match->named($key) for pulling out a named capture

        Use Try::Tiny to avoid swallowing exceptions (rafl)

0.16 Sun Oct 17 2010
        ** BACKWARDS INCOMPATIBLE CHANGE: Pass the match object into rule
        **    blocks rather than assigning $1, $2, $3. Use ->pos(1), (2), (3),
        **    etc. instead. This cleans up the code a lot and makes
        **    Path-Dispatcher more flexible.

        Add support for named captures

        Make all attributes read-only. If you need something to be read-write,
            I am open to such a change. Just let me know!

        Make _dispatcher_rule private

        Remove trace/readable_attribute/name support. This wants to be
            implemented in a different, better, more comprehensive way.

        Add documentation for shell tab completion

        Plenty other updated documentation

Log message:
Revision bump after updating perl5 to 5.14.1.

Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!

Log message:
Updating devel/p5-Path-Dispatcher from 0.14 to 0.15

Upstream changes:
0.15 Tue Mar 16 09:40:40 2009
        ** Factored Path-Dispatcher-Declarative into its own distribution
        ** Be sure to update your dependency information!

        * Implement ->complete for Rule::Dispatch
        * Add Path::Dispatcher::Rule::Alternation
        * Implement case insensitivity fory Rule::Eq
        * Add Path::Dispatcher::Rule::Sequence - like Rule::Tokens but
            better!
        * Add Path::Dispatcher::Rule::Enum
        * Path autoboxing has been factored out into a private method for
            more overridability
        * A few documentation improvements as usual :)

Log message:
Updating devel/p5-Path-Dispatcher from 0.13nb1 to 0.14

Upstream changes:
- none noted -

Log message:
Bumping revision of packages which depend direct or indirect on
devel/p5-Class-MOP. A late detected incompible change forced it.

Log message:
Updating package devel/p5-Path-Dispatcher from 0.12 to 0.13

pkgsrc changes:
  - Adding license

Upstream changes:
0.13 Sun Aug 9 13:38:19 2009
        Add unshift_rule to classes that do Role::Rules
        Several distribution improvements

Log message:
Initial import of p5-Path-Dispatcher version 0.12 in the NetBSD
Packages Collection.

The Perl 5 module Path::Dispatcher is similar to the module
Jifty::Dispatcher but its use is for the command line.

The basic operation is that of dispatch. Dispatch takes a path and
a list of rules, and it returns a list of matches. From there you
can "run" the rules that matched. These phases are distinct so that,
if you need to, you can inspect which rules were matched without
ever running their codeblocks.