Looks like there are several answers depending on what you want to do. There is a distinction between package namespaces, modules and distributions.

If you are wanting to take a snapshot of all namespaces that have been used, at a particular point during execution, you can, as PodMaster has suggested, use Devel::Symdump. Or you can walk through the symbol table yourself:

all_below('Foo::');

sub all_below {
    my $ns = shift;
    no strict 'refs';
    ( $ns, map { (/::$/ && !/main::/) ? all_below($ns.$_) : () }
        keys %$ns );
}
[download]

But if you are looking at determining dependencies without running any code, this won't include everything, but Module::ScanDeps has a good attempt at finding everything used or required.

As you pointed out, any .pm module can potentially put stuff into any namespace, and it's a matter of convention and etiquette that we don't lose control of namespaces.

In terms of distributions, the META.yml and the .packlist file (written by make install) list out which .pm modules are installed by a distribution.

Hope this helps.

Thank you and PodMaster, I followed your advices. Moreover, I rethought the design and put restriction for myself: to preload all Foo::Basic::* modules with use Foo. I't all kind of plugins (Foo::Plugin::*), with overloading basic system functionality (Foo::Basic::*), so this way I always know what Foo::Plugin::* modules to search (for each Foo::Basic::*) to try to require them.