Perl 5.18.1 binary kits for OpenVMS available

[Craig A. Berry]

Installation kits for OpenVMS Alpha and OpenVMS I64 v8.3 and later are available at:

<https://sourceforge.net/projects/vmsperlkit/files/>

The files are self-extracting archives and after downloading
you must run them like so:

$ run VMSPORTS-AXPVMS-PERL-V0518-1-1.SFX_AXPEXE

for Alpha, and:

$ run VMSPORTS-I64VMS-PERL-V0518-1-1.SFX_I64EXE

for Itanium. Then, on either platform:

$ product install perl

and follow the usual installation prompts.

Have an appropriate amount of fun. Anything related to these kits that turns out to be more fun than you can handle is probably best reported on the vmsperl mailing list.[1]

[1] <http://lists.perl.org/list/vmsperl.html>

________________________________________
Craig A. Berry
mailto:craig...@mac.com

"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser

[John E. Malmberg]

On 9/1/2013 3:55 PM, Craig A. Berry wrote:
> Installation kits for OpenVMS Alpha and OpenVMS I64 v8.3 and later are available at:
>
> <https://sourceforge.net/projects/vmsperlkit/files/>

To use this perl with Bash 4.2.45 and GNV, add the following 2 line file
to gnv$gnu:[usr.bin]:

$ type gnv$gnu:[usr.bin]perl.
#! /bin/sh
/perl_root/perl $*

Can this be added to the release notes as an optional post installation
task?

Also, the release notes are referencing "README","INSTALL","artistic.",
and "copying" files that I can not find in looking in PERL_ROOT:[*...].

Regards,
-John
wb8...@qsl.network

[Craig A. Berry]

On Sep 15, 2013, at 7:26 PM, John E. Malmberg <wb8...@qsl.net> wrote:

> On 9/1/2013 3:55 PM, Craig A. Berry wrote:
>> Installation kits for OpenVMS Alpha and OpenVMS I64 v8.3 and later are available at:
>>
>> <https://sourceforge.net/projects/vmsperlkit/files/>
>
> To use this perl with Bash 4.2.45 and GNV, add the following 2 line file to gnv$gnu:[usr.bin]:
>
> $ type gnv$gnu:[usr.bin]perl.
> #! /bin/sh
> /perl_root/perl $*
>
> Can this be added to the release notes as an optional post installation task?

Not release notes, as that's just the latest perldelta, but it sounds reasonable to put it in the post-installation tasks for the PCSI kit. I'll look into it.

> Also, the release notes are referencing "README","INSTALL","artistic.", and "copying" files that I can not find in looking in PERL_ROOT:[*...].

Those refer to files in the source distribution. The file that I'm distributing as release notes is just the perldelta.pod documentation file that documents changes since the previous release. I can understand the confusion of having files mentioned that are not in the binary kit, but it's not a platform-specific problem. Not sure what a reasonable solution is.

You can always get the license like this:

$ perldoc Artistic