In the context of a code quality reporting toolkit and the recent change in community licensing term for Active Perl, there are few questions that we are faced with:
1. Does the use of Active Perl during the development of an internal quality reporting toolkit still qualify under community licensing?
2. Can the project teams using the toolkit still use community license to use the Active Perl on their internal build machines in order to use the toolkit?
3. What are the approximate pricing for the Enterprise License (~100 installs) and OEM License.
I am using ActivePerl in an automated / continous integration system (jenkins).
During the job i try to install ActivePerl on Windows / Linux machines.
This is ok for linux, cause ActivePerl is provided as package, and installer has several commandline options to install as non-root user
On Windows it is hell!
1) Officialy only msi packages are available. I took me some time to detect, that there are also zip files availabe for download. Couldn't these be added to the download page? Or the folder be linked there to get them?
Running AIX 5.3 PowerPC.
Trying to install Perl (ActivePerl-188.8.131.525-aix-184.108.40.206-cc_r-296746).
File copying works.
Install of ActivePerl to /opt/ActivePerl-5.14 failed:
I just upgraded to Perl 5.16.3 (on Win 2003) due to an "ActivePerl Heartbleed Security Update" email from activestate. After the upgrade my plx scripts stopped working on my web site. I checked IIS and it was set correctly to map plx to c:\perl\bin\perlis.dll.
I checked and perlis.dll did not exist! I ran the installer again and checked PERL ISAPI and I got: "Use of this feature requires a Business Edition license". WTF!? When did this start? Can anyone help me with this?
I'm trying to automate ActivePerl installations on Windows, referencing the following document:
What I've noticed is that the TARGETDIR is actually a base directory. If I want to install the win32-x64 ActivePerl to c:\perl, I can't do that. Specifying a TARGETDIR of c:\perl ends up creating c:\perl\perl64.
I am working on migration of a legacy application that uses ActivePerl on Windows 2000 server.
Can ActivePerl run on 32-bit or 64 bit Windows Server 2008 and Windows Server 2012?
I would like to develop a desktop app for windows 8.1 using ActivePerl. The most recent version of ActivePerl 5.18.2 depends on MSVCRT.DLL - as far as I understand MSVCRT.DLL cannot be used in a Windows 8.1 store app, MSVCR110.DLL and related DLLs should be used instead. Since Microsoft is forcing the move to Window 8.1 will ActivePerl for Windows 8.1 be compiled against MSVCR110.DLL and related runtime libraries?
this question has been resolved via a support ticket.
I tried yesterday update to newest AP 220.127.116.111 and have not succeed to get it working.
Firstly uninstalled completely previous perl. Then new install to the same directory, and perl is crashing on most of my existing scripts that were working with perl 5.16. I think the bug which was already present in AP 5.18.1 is still present (wrong linkage to perl516.dll). Anyway I didnot manage any of 5.18 perls fully functional and I did update this software many times. So I assume there's something wrong with all 5.18 builds.
I work for a company which is currently using AP 5.8.822 on their 2003 box and have quite a few Perl scripts. I see in the AS 5.16 documentation, it says build 16xx is incompatible with previous version's binaries, though I'm not sure what that entails.
If we were to upgrade to 5.16.x as I have on my PC, would it break all of the existing Perl scripts written and used in the 5.8.822 environment? I would like to upgrade so I can use the remove_tree function and output to a scalar variable for logging purposes, as opposed to just the spray and pray of rmtree.