Newest Perl on Win without ActiveState or Strawberry

After updating git-portable I do have a Perl 5.36 operating on Windows.

Which is a bit surprising given all the struggle Strawberry is going thru.

I remember there might be "restrictions" with this since it's optimized to work inside bash and expects *nix path conventions. But I'm wondering - well meditating - if this might not be a viable substitution for Strawberry.

I also suppose that the c-compiler/make combo might cause problems when installing further modules ... (?)

But portable means one could keep an unaltered git version in one directory and adjust another in a second directory...

Opinions?

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}

update

for a similar recent discussion see Perl::Dist::APPerl - Actually Portable Perl

Comment on Newest Perl on Win without ActiveState or Strawberry

Replies are listed 'Best First'.
Re: Newest Perl on Win without ActiveState or Strawberry by haj (Vicar) on Jan 13, 2023 at 16:11 UTC
Which is a bit surprising given all the struggle Strawberry is going thru. Strawberry isn't just Perl. It is a Perl distribution. Perl, plus 484 non-core Modules, plus 42 external tools. You need to "expand" the lists in the release notes to see them all. Most of the struggle is getting the external tools compiled on Windows, and to have some decent automation for that process. Once the external tools are done, it should be fairly straightforward to install the non-core XS modules (pure Perl is easy anyway). But congratulations, the first step is done!	[reply]

Replies are listed 'Best First'.

Re: Newest Perl on Win without ActiveState or Strawberry
by haj (Vicar) on Jan 13, 2023 at 16:11 UTC

Which is a bit surprising given all the struggle Strawberry is going thru.

Strawberry isn't just Perl. It is a Perl distribution. Perl, plus 484 non-core Modules, plus 42 external tools. You need to "expand" the lists in the release notes to see them all.

Most of the struggle is getting the external tools compiled on Windows, and to have some decent automation for that process. Once the external tools are done, it should be fairly straightforward to install the non-core XS modules (pure Perl is easy anyway). But congratulations, the first step is done!

[reply]