This is true, but AS licensing agreements from years ago prohibited that for actual product shipment. I don't know what current AS licensing says for a re-distributed product. I suspect potential legal trouble if this is done for end-product distribution vs perhaps in-house use.
At the time, I bought a Perl Dev Kit license and generated an .exe file for just that legal reason. Of course the Dev Kit has been discontinued.
AS did have some tools for "cloning" an installation. You ran a utility to make an XML file. You installed Perl directly from AS (no binary distribution allowed) on the target machine. Then there was a utility that used this XML file which was supposed to re-create the environment on the target machine. I had trouble with that and I think many others did too.
The new AS way is to create an account on their site and have AS build a version for you with the modules that you need. The result of this is an installable MSI file or equivalent in the Unix world. That AS built version (which includes XS binaries for your platform) can be freely re-distributed without restriction. In the Windows world, this is good. There of course can be complex issues with multiple Perl versions on any platform.
In reply to Re^2: Replicate Perl setup
by Marshall
in thread Replicate Perl setup
by nikosv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |