On Mon, 07 May 2007, Mark Dootson wrote: > It is probably possible but it is a generally accepted interpretation > of the Perl License that you may not create executables with a > packager (PAR, PerlApp etc) that can run arbitrary external perl > scripts on systems without a Perl installed. > > So, having an executable mypacked.exe > > that can do > > mypacked.exe anyoldscript.pl > > on a system without Perl installed, is at the very least in a grey > area as far as the Perl License is concerned. > > I only post this to flag up a potential issue that you may not have > considered. I may be completely wrong and "mypacked.exe > anyoldscript.pl" might be fine. I just always understood that you > could not do this and should distribute Perl instead.
I think this is just a limitation of the ActiveState Perl Dev Kit license, and PAR shouldn't have any such limitations. The limitation is in the PDK license to prevent people from packaging a trivial wrapper app with PerlCtrl, PerlNET, PerlSvc or PerlTray, and then basically redistributing just the functionality of the PDK tool without adding any value of their own. The restriction isn't really meant to limit what you can do with PerlApp. And anyways, you can always send an explanation of what you want to do to ActiveState to get this restriction waived for your application. Cheers, -Jan
