Thanks!
I probably end up having same version in all modules.
Immediately after I released "release" CPAN version of my script (previously I had "unzip-and-run" version), one of my users messed up files somehow of old and new version.
Thus I add version to all files (that solved all of problems in original post, btw), and wrote code like this to check version runtime: 
    for (keys %INC) {
        if (/^App\/MtAws\/(.*)\.pmc?$/) {
            my $module = "App::MtAws::$1";
            my $got = $module->VERSION;
            $got = 'undef' unless defined $got;
            die "FATAL: wrong version of $module, expected $VERSION, f
+ound $got" unless $got eq $VERSION;
        }
    };
}

[download]

In reply to Re^4: Understanding CPAN indexing by vsespb
in thread Understanding CPAN indexing by vsespb

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.