Re: ActivePerl, Licensing and PAR

As I read the licenses, you should be OK to publish works that you created using ActiveState tools. However, since I'm not the one who gets into trouble if I'm wrong, you would be better off checking with the company itself. Even then you could theoretically have problems, since whoever answers might not have authority to speak on the subject. Still, if you troubled to ask, and someone there gave you the OK, it would go far to protecting you.

Comment on Re: ActivePerl, Licensing and PAR

Replies are listed 'Best First'.
Re^2: ActivePerl, Licensing and PAR by anisotropic (Initiate) on Jan 30, 2006 at 19:27 UTC
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. =)	[reply]

Replies are listed 'Best First'.

Re^2: ActivePerl, Licensing and PAR
by anisotropic (Initiate) on Jan 30, 2006 at 19:27 UTC

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. =)

[reply]