Final Version pairings for ActivePerl with Perl Dev Kit

Question: 

I want to upgrade ActivePerl and my Perl Dev Kit. What's available?

Answer: 

------------Update April 2019---------------------
Advisory:
If you still have a working instance of the Perl Dev Kit, DO NOT alter it.
- Do not attempt to move it to a newer system.
- Do not attempt to update to a newer version of Perl
- Do not attempt to update to a newer version of the Perl Dev Kit
- Do not attempt to update any modules from PPM
- Do not install system updates
All of these actions carry varying levels of risk, ranging from very high to moderate, of rendering your Perl Dev Kit instance abruptly and irreparably broken.

PDK has been discontinued for three years. All users need to be winding down any use of the Perl Dev Kit as rapidly as possible.

-------End of Update----------

You may have already seen the announcement... Last year, ActiveState announced that the direction for the company's future will be OpenSource Languages.

http://www.activestate.com/blog/2016/11/activestate-open-source-language...
http://www.activestate.com/blog/2016/12/open-source-languages-company-up...

Proprietary tooling for certain languages is not part of the OpenSource Languages Company future. Sales of both of the Dev Kit tools sets were discontinued at the time of those announcements. New licenses for PDK and TDK will not be available as separate products.
http://www.activestate.com/perl-dev-kit

Engineering and Development time and resources were immediately priorized for updating the existing language distributions. In 2017, work is starting on the new languages. Work was stopped on PDK, and that means that there will not be a PDK 9.6.

Existing copies of PDK 9.5.1 cannot use the latest releases of ActivePerl. The 2203 and 2204 builds are not compatible, and all 5.24 versions remain incompatible with the final release of PDK 9.5.1.

----Update September 2017------

Since the End of Sales for PDK, there have been enough newer versions of Perl released by the Perl Community that none of ActivePerl versions compatible with the Perl Dev Kit are still Supported by the Community. With no supported, free, versions of Community Edition ActivePerl available, Users of the Perl Dev Kit will need at least a Business Edition license to access a compatible version of ActivePerl.

-------End of Update----------

2202 is the last compatible ActivePerl, except on OS X.

For OS X, the 9.5.1 release of PDK was created on OS X 10.5. Every PDK must have a 100% binary compatible ActivePerl. ActivePerls switched from building on OS X 10.5 to building on OS X 10.9 at 5.22.2.2202 and are now 64-bit only. These two factors are responsible for the unresolvable symbols error message. Since there will not be a 9.6 that is also built on OS X 10.9, the 2201 release is the last ActivePerl that is compatible.

HeartBleed vulnerability and ActivePerl

Question: 

Is my Community/Business/Enterprise Edition version of ActivePerl vulnerable to HeartBleed?

Answer: 

ActivePerl Community/Business Editions which, as shipped, are affected:
- 5.14.4.1405 - upgrade to 5.14.4.1406 (Business Edition only) or 5.16.3.1604 to fix
- 5.16.3.1603 - upgrade to 5.16.3.1604 to fix
- 5.18.1.1800 - upgrade to 5.18.2.1802 to fix
- 5.18.2.1801 - upgrade to 5.18.2.1802 to fix

Modules supplied through PPM are unaffected.
Modules compiled locally must be reviewed locally for vulnerability.

Enterprise Editions can be distinguished from Community/Business Editions by the presence of an additional fifth number before the six digit build number/version control number.
ActivePerl Enterprise Editions which, as shipped, are affected:
- 5.8.9.829.9 through 829.12
- 5.10.1.1009.9 through 1009.12
- 5.12.5.1206.2 through 1206.5
- 5.14.3.1404.2 through 1405.3
- 5.16.2.1602.2 through 1603.3

New Enterprise releases have been issued and can be located under the 2014Q1.1 folder.

HeartBleed vulnerability and ActivePython

Question: 

Is my Community/Business/Enterprise Edition version of ActivePython vulnerable to HeartBleed?

Answer: 

No Enterprise versions of ActivePython are vulnerable.

No Community/Business Edition versions of ActivePython 2.x and no Community/Business Edition versions of ActivePython 3.0, 3.1, and 3.2 are vulnerable to HeartBleed.

Only Community/Business Edition ActivePython 3.3.2.0 and 3.3.4.1 are vulnerable.
An updated 3.3 release will be needed to address the vulnerability.

32 bit installers for ActivePerl Community Edition

Question: 

Where can I find 32 bit versions of the latest ActivePerl releases?

Answer: 

ActiveState is no longer producing free versions of any language distribution for 32 bit operating systems.

32-bit variants of older releases will require Business Edition to access installers.

32-bit variants of new language versions may be available under ActivePerl Enterprise contracts for some 32-bit operating systems.

https://www.activestate.com/compare-editions

Unattended Installation

Question: 

How do I get the installer for Community Edition to run in a silent, unattended mode?

Answer: 

See the Installation guide for the product in question.

Documentation on unattended installation is limited in scope because the functionality is limited. There are many outcomes which might be desired that the command line for the exe installer cannot support.

Unattended installation under the Community Edition license is Strongly Discouraged.
A requirement for unattended installations is associated with use cases that are Beyond Development, or are OEM Redistribution.
- Commercial entities must have a senior license for use Beyond Development.
- All cases of Redistribution must have a senior license.
Without the opportunity to review the terms of the Community Edition license, an end-user will be liable for complying with the license without being aware of the terms.

For ActivePerl, Legacy Build or Enterprise Edition versions can provide an MSI style installer with more extensive support for unattended installations.

New to Go on Windows

Question: 

I'm new to Go. I've installed ActiveGo. How do I get started?

Answer: 

Start here:
http://docs.activestate.com/activego/1.8/doc/code.html
The introduction will explain how your workspace is arranged. In case you missed it, your $GOPATH has already been set by the ActiveGo installer.

If you don't use Git already, you should install it and learn how to use it. Git is an essential supporting tool for coding in Go.

There's a simple HelloWorld program in the Go introduction.

ActiveGo sets up local documentation on your system as a document server. On the local ActiveGo documentation start page, there is an interactive Sandbox window labelled "Try Go". You will see the source code before it compiles. When you click "Run" the code compiles and displays the result in the box below the source code. There's a pull-down with a small set of sample Go snippets.

Multiple versions of Go

Question: 

Can I have ActiveGo and another distribution of Go installed together?

Answer: 

The ActiveGo-beta will set GOROOT, GOPATH, and PATH variables. The Golang distribution will also set GOROOT and PATH.

-ActiveGo will always be the default version of Go if both are on the system due to the ways both Go versions set up PATH. Neither ActiveGo nor Golang Go will remove the other distribution from PATH.

-Any value in GOROOT will be overwritten by both versions of Go when they install. The last version to install will be set up as the root. If you remove a version of Go, you will need to re-install/repair the other one to ensure that GOROOT is correct before you start using it.

-GOPATH is your personal workspace. Your workspace should be usable with either version of Go.

ActiveState PPM Availability and the 401 error

Question: 

PPM gives me a 401 Authorization Required. Why?

Answer: 

--------
UPDATE (Oct 2016): This FAQ was originally posted in 2010. If you are running a version of ActivePerl that gets a 401 error when it contacts a Business Edition Only repository, our advice has evolved. Now, you should replace that ActivePerl.

A "401" error when contacting PPM should now be treated as a indication of obsolesence.

Later versions of ActivePerl that fully support Business Edition Licences have a more informative error message instead of the basic "401". Old ActivePerls that can only report a "401" will not support a Business Edition licence if one is installed. An ActivePerl that reports a "401" from PPM is probably not compatible with your current operating system either.

---------
Original FAQ:

The repository you are accessing contains exclusively Business Edition content. If you do not have a Business Edition license installed on the system, the PPM server will advise that you are not permitted to access the directory.

Perl versions move into Business Edition when the Perl Community is no longer actively supporting that version of Perl. ActiveState policy for PPM is that free and open access to PPM binary modules for versions that have moved entirely into Business Edition will continue for *at least* six months beyond the date at which the no Community Edition versions of that Perl are available.

All versions of Perl 5.8 and 5.10 required Business Edition licensing in 2010. ActivePerl 5.8 builds older than build 829, and ActivePerl 5.10 builds older than 1008 must use the manual download process described in this FAQ:
http://community.activestate.com/node/8128

All versions of Perl 5.12 required Business Edition licenses as of September 2012. All ActivePerl 5.12 builds can use the normal PPM client with a Business Edition license installed, or the manual download process.

ActivePerl 5.14 requires a Business Edition license as of October 2013 for access to installers. PPM access for modules other than the installers remains free as of December 2013.

Recovering Sourcecode from wrapped files

Question: 

Can you help me recover the original source code from my executable file?

Answer: 

The Support and Maintenance package for Perl Dev Kit does not include recovery of lost source code, and we do not have any special internal tools for reverse engineering wrapped code.

We recommend the use of distributed version control systems during development. Free services are available, and they provide many useful features in addition to ensuring that source code is not lost. Regular backups are still an alternative if you don't want to use version control.

0.1
Brad Grant
Thu, 2016-07-21 06:01
  • : 6.0 - 10.*
  • : 6.0 - 10.*

This is a keyword and syntax highlighting extension to give basic support for *.awk files in Komodo Edit.