Hi, I work for ActiveState, and I think I can (hopefully) clear this up.

The ActiveState Community License is not designed or intended to restrict packaging Perl applications using utilities such as Perlapp, PAR, or perl2exe. Specifically, we do not have a problem with people packaging their applications in this way using the parts of ActivePerl that are licensed under the Artistic license ( core Perl and the bundled CPAN modules that are included ).

There are some restrictions related to ActivePerl, but these are not intended to restrict packaging applications. They are in fact intended to restrict the following:

• re-packaging / re-branding ActivePerl in any way
• redistributing any of the proprietary Activeperl features eg PerlScript, PerlIS, PerlEx, etc.
• redistributing ActivePerl as a whole without an OEM license in place.

It is not our intention to use licensing as a way to force people to use Perlapp; we would rather people buy the PDK instead because it is awesome. =)