in reply to FatPacker vs PAR

Current choices
  • PAR/pp works for everything.
  • CAVA pack works for everything.
  • perl2exe works for everything.
  • perlapp works for everything.
Honorable mention
Work
"Current choices" are the only choices to consider, they all work about the same, and they're all current, and they work.

"Honorable mention" also work, but they either do more, or do less, or ... if you have a need for such, you already using them, for example to enhance the "Current choices".

"Work" are sometimes basic, sometimes outdated, sometimes experimental ... fancy toys :) More work than solution :) Respectable, workable, but still work :)

Replies are listed 'Best First'.
Re^2: FatPacker vs PAR
by Anonymous Monk on May 12, 2011 at 00:46 UTC
    Thanks for the nice summary!

    I toyed around with PAR yesterday. It has a lot of features but I had a few issues with it:

    First, it extracts everything the first run to /tmp/par-$USER/cache-$GUID/. This makes the startup of the first run noticably slow. It doesn't share the cache with other users or even different version of the same binary. And of course, it seems inelligent? I thought the point of using zip is so that we can have a virtual filesystem and modules can be loaded on demand from it?

    Second, filters didn't seem to work on modules added via -a/-A. Tried the -F option (as well as the -f, which works) with the Squish and Crypto filters. The modules extracted to the cache were all unfiltered. I might have to fiddle with it some more.

    I'm going the FatPacker route. It seems far simpler and fits my need for now.

[reply]

      If You are on a GNU/Linux platform You can try staticperl, that generates a binary executable from Your program.

      :)))))
[reply]

In Section Seekers of Perl Wisdom