Yes, a possible solution is to not use PAR at all! You can replace: 
use PAR;
use lib 'Bam-Kapow';

[download]
(a.k.a. use PAR 'Bam-Kapow';) by: 
BEGIN {
  use Archive::Zip;
  my $zip = new Archive::Zip('Bam-Kapow.par');
  $zip->extractTree('', 'shazam/');
  use lib 'shazam/lib';
}
END { use File::Path; rmtree 'shazam/'; }

[download]
which produces the output: 
Using Bam::Kapow version 0.01
MOTD: Message of the day: PAR rules!

Got Bam::Kapow from shazam/lib/Bam/Kapow.pm

[download]
Of course, it would be nicer if PAR provided an option to do that, something like: 
use PAR 'extract';

[download]
which would make it behave the same way it does when it's wrapped up in an executable.

In reply to Re^2: Data files in a .par file by Tortue
in thread Data files in a .par file by BooK

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.