I discovered that my current AS perl, 5.12, is no longer ppm'able [without a business license] so I'm upgrading to 5.16. I'm worried about how that 'upgrade' should/will go. right now perl is installed in c:\perl64. Can I just install the new 5.16 in the same directory and will it basically leave my installed modules and other such along [perhaps needing a big update via ppm, but still there]? Or will I run into problems?
Can't get the PPM GUI to run. This is on Win 7 64-bit. Tried reinstalling 5.16.2 64-bit, with the same result. PPM command line seems to work. Just the GUI won't run. Tried 5.16.2 x86 and this launches the GUI fine.
The following is in the event log:
Faulting application name: perl.exe, version: 188.8.131.522, time stamp: 0x50d17d90
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
Exception code: 0xc0000005
Fault offset: 0x0000000000036b3b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Frequently encountered problems may have an FAQ available.
I've just installed ActivePerl 184.108.40.2064 and when I run perl -V, I see that @INC doesn't include the "site/lib" directory? This is the end of the perl -V output:
Characteristics of this binary (from libperl): Compile-time options: HAS_TIMES HAVE_INTERP_INTERN MULTIPLICITY PERLIO_LAYERS PERL_DONT_CREATE_GVSV PERL_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS PERL_MALLOC_WRAP PERL_PRESERVE_IVUV PL_OP_SLAB_ALLOC USE_ITHREADS USE_LARGE_FILES USE_LOCALE
I'm using Active Perl and the Perl Package Manager for a project for a grad student. I am using ActivePerk 5.16.2 Build 1602. I'm on Windows 7
I'm trying to install 2 packages, but the "Mark for Install" button is grey-ed out and I can't click (similarly, if I search for the package name and right click it, I see the option to Install it but it is also grey-ed out). The packages I would like to install are for 2.30 and 1.13
Every time I load PPM, I get this window:
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-220.127.116.115-aix-18.104.22.168-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.