Re^5: CPAN Installation of Perl Packages Fails

I agree with you about preferring Strawberry Perl over ActivePerl.

However, you can use PPM to install MinGW and dmake for ActivePerl so that you can install directly from CPAN. Also, according to this blog post, it looks like ActiveState has decided to start moving away from using their own package managers for their distributions of programming languages and will rely more on the community package repository for each programming language. For ActivePerl, that means support for install modules directly from CPAN.

Comment on Re^5: CPAN Installation of Perl Packages Fails

Replies are listed 'Best First'.

Re^6: CPAN Installation of Perl Packages Fails
by afoken (Chancellor) on Jun 23, 2017 at 06:21 UTC

However, you can use PPM to install MinGW and dmake for ActivePerl so that you can install directly from CPAN.

That's what I tried to say with "A working build environment was only recently added as an optional package."

it looks like ActiveState has decided to start moving away from using their own package managers for their distributions of programming languages and will rely more on the community package repository

That sounds like a good idea, and it is a logical consequence of providing a build environment package. ActiveState could not stop people from using CPAN anyway, and even less after providing the build environment.

To be fair, I haven't used or even followed the changes in ActivePerl. For me, it is obsoleted by Strawberry Perl, and so I feel no need to follow what happens in ActivePerl.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]


Don't ask to ask, just ask
	PerlMonks