That only searches one of @INC's directories, and it has portability issues. Fix: 

use Path::Class  qw( dir );
use Scalar::Util qw( reftype );

my $base_pkg = __PACKAGE__ . '::Plugins';

my %plugins;

my @subdirs = split(/::/, $base_pkg);
for (@INC) {
    next if reftype($_);

    ++$plugins{"{$base_pkg}::$_"}
        for
            grep /^\.pm\z/,
            map $_->basename(),
            grep !$_->is_dir(),
            dir($_, @subdirs)->children();
}

( my $base_dir = $base_pkg ) =~ s{::}{/}g;
++$plugins{"{$base_pkg}::$_"}
    for
        map m{^\Q$base_dir\E/([^/]+)\.pm\z},
        keys(%INC);

my @plugins = sort keys(%plugins);

# Load them all!
for my $plugin (@plugins) {
    eval("require \E$plugin\Q")
        or die("Loading plugin $plugin: $@");
}

[download]

You gotta be careful that the file name case matches the package name case on case-agnostic systems. You've got a problem if there's a caseless system out there. Maybe some heuristics would help (such as scanning the .pm for a matching package statement and use its case).

Scanning %INC is useful for getting around the problem of a package manager creating a virtual file system using a reference in @INC.

In reply to Re^2: How to see what is available in Module::Namespace::* by ikegami
in thread How to see what is available in Module::Namespace::* by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.