in reply to ActivePerl, Licensing and PAR
Why don't you email ActiveState? I would direct this question directly to them and not this forum. PAR is a free alternative to some of the commercially sold tools ActiveState sells, namely PDK (PerlDevKit), so I can see them adding terms to their copyright that would protect their work from being included in works distributed externally (presumbably for a profit). If you are not going to keep it in your organzation, then you can always purchase PDK Deployment Tools and use PerlApp to build your app, else, if you want to save the $145, build your own Perl distribution and use PAR with that.
Re^2: ActivePerl, Licensing and PAR
by TGI (Parson) on Jan 30, 2006 at 07:36 UTC
|
I did contact AS for clarification on this issue, and got no reply.
PDK is a useful tool, as is PAR; I'd hate to be forced to give either of them up. For my particular app, the PDK package starts noticeably faster than the PAR package--that was enough to justify the expense for me.
I would never have experimented with packaging perl apps like this if PAR wasn't available. AS sold me a license of PDK because I made a decision based on my evaluation and successful use of PAR.
My good will toward AS would be pretty much wiped out if they pulled a licensing maneuver and banned use of PAR with ActivePerl.
| [reply] |
|