first of all, if you're uncertain about PAR features/behaviours, just ask PAR people.
Fortunately there's mailing list par@perl.org, subscribe by writing a letter to par-subscribe@perl.org. I very doubt they're unresponsive, so they'll shed a light quickly.
(same for Tcl::Tk mailing list tcltk@perl.org)

On the speed - after PAR cached its unZIP (after its first run), it will be very the same as within perl library itself, just with slightly different @INC path, it should be reasonably slow only first time. (this is all configurable, AFAIK)
But if you do want speed boost within perl/Tk apps - go to Tcl::Tk, its faster x2, in addition to be more flexible. Yet perl's memory allocator is a win on win32.

Actually I agree on all your points about PAR and perl2exe (I meanHDD and opensource)
Moreover, I suspect that commercial packers go very same way as I did, but their added value is not very deep, its quite near on the surface...
they did more testing than I did and wrote code, but essential part is small. Perl is almost redistributable without additional packers.

An essential additional remark:
I did several versions of bootstrap mechanics of what you've just reviewed, WRT who unzips the file module/perl58.zip
In some versions its Perl's Archive::Zip, but in the version you've tried this is Tcl/Tk's unzipping.
If moving to CPAN, then Perl-only solution is preferred, but Tcl/Tk way was faster in this particular case
(usually perl faster than tcl/tk a bit, but extracting members from perl58.zip was faster in Tcl/Tk because it was implemented in C internally)

Sometimes I just scared on how many ways to do things. TIMTOWTDI.
Best regards,
Courage, the cowardly dog...
... err, Vadim.

In reply to Re^16: problem with par as other user by vkon
in thread problem with par as other user by Anonymous Monk

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.