ActiveState Community

PerlDevKit is a collection of tools. The contents of the collection varies by platform because some tools are restricted to certain operating systems.

All 64-bit platforms are restricted by a lack of UI support. The tools that are found only in PDK Pro collection are UI-based, so we don't try to sell you licenses for something that we can't provide.

All the 32-bit tools will run on 64-bit machines, so if you want the GUI functionality, you can install the 32-bit PDK Pro and a 32-bit ActivePerl to get the required GUI support. The extra advantage and purpose of having the 64-bit PDK Deployment tools is to provide the few tools for which you might need native 64-bit apps (primarily PerlApp to wrap and deploy a 64-bit Perl application).

PerlNET in PerlDevKit 7.2.0 requires .NET 1.1 and .NET 2.0, with SP1 for both being strongly recommended.

In Case #1 there is no .NET installed. PDK detects this and automatically disables PerlNET.
In Case #2 only .NET 1.0 is installed.
In Case #3 only .NET 1.1 is installed.

You have two options. You can either install .NET 1.1 and .NET 2.0, then proceed with a full installation of PerlDevKit, or you can disable the PerlNET component of PerlDevKit during the PDK installation process (as is done automatically in Case #1). Either should allow you to complete the install.

Occasionally when you are installing a new ActiveState license or starting a trial or beta product that installs a temporary license you will get the following message:

Can't create '/Users/myusername/Library/Application Support/ActiveState/ActiveState.lic

This is due to the directory the license is being installed in being owned by another user or not having the appropriate permissions. The easiest way to fix this is from the Terminal, by typing the following two commands:

sudo chown -R myusername /Users/myusername/Library/Application\ Support/ActiveState
chmod 0755 /Users/myusername/Library/Application\ Support/ActiveState

You may have to enter your password after typing the first command. This is normal, and required because you are executing that command as root (which is needed to change the ownership of files not owned by the current user).

Since 8.4.8, automated installation was included but not published or
documented. The following documentation comes straight out of the comments
in the installer code:

--directory DIR

The installer goes auto and installs the distribution
into the directory DIR. The directory for the demos
is derived from that, it is DIR/demos. This can be
overridden. See below. The runtime directory is DIR as
well. This can be overridden. See below.

--demo-directory DIR

Overrides the location of the demo directory. See above.
The option is ignored if the installer is not in auto-mode.

--runtime-directory DIR

Specify directory to patch in. Optional. Ignored if
automatic mode was not activated with --directory.
Ignored on Windows.

--user-mode

Windows only, ignored on Unix. Install for the current
user. Default is to install for all users, i.e. admin-mode.
The option is ignored if the installer is not in auto-mode.

--no-plugin

Deactivates the installation of the plugin and all related
stuff. Optional. Default for automatic mode is to install
the plugin. The option is ignored if the installer is not in auto-mode.