Re^2: Installing Perl Modules

"I have internet access but these sites are blocked for downloading contents(error code - 500). Also PPM GUI shows very less no. of modules as it is not able to synchronize due to corporate restrictions."

The link I provided you earlier (Yes, even you can use CPAN) touches on all of these points, management buy in, corporate policy etc, please read them and consider resolving the issue within your organisation or client. I faced this issue until working through it with our client. The process will be different for each organisation.

"Can I get manual installing instructions for C based modules anywhere. Like which file to place where etc.??"

It's not always quite that straightforward, consider using the ActiveState documentation for configuration of the development tools (which you will still have to download and install). I've not had to do this for years.

Update: PPM allows local installations Re: Problems installing new Modules for ActiveState v 5.10.

Comment on Re^2: Installing Perl Modules

Replies are listed 'Best First'.
Re^3: Installing Perl Modules by MidLifeXis (Monsignor) on Aug 29, 2016 at 18:24 UTC
The process will be different for each organisation. It may be anywhere from "Oh, we didn't realize you needed that, here is a change to the FW rule" to "Provide a risk analysis for each version of each module that you will need (and dependencies) and we will stash it in a corporate CPAN environment that you can use" to "Not on your life - intertubes bad" (ok, some places that is a valid stance, but I have seen it be just an "easier to block this than deal with it safely") approach. Communication with management about this stuff is good. If you can present it in a cost/value type of comparison, then management can do their job and either buy in, or reject it. If not authorized to make a decision yourself, all that you can do (well, legitimately) is provide information to those that are. There may be a valid risk that you have not yet considered, or a benefit that they have not. Good luck! --MidLifeXis	[reply]

Replies are listed 'Best First'.

Re^3: Installing Perl Modules
by MidLifeXis (Monsignor) on Aug 29, 2016 at 18:24 UTC

The process will be different for each organisation.

It may be anywhere from "Oh, we didn't realize you needed that, here is a change to the FW rule" to "Provide a risk analysis for each version of each module that you will need (and dependencies) and we will stash it in a corporate CPAN environment that you can use" to "Not on your life - intertubes bad" (ok, some places that is a valid stance, but I have seen it be just an "easier to block this than deal with it safely") approach.

Communication with management about this stuff is good. If you can present it in a cost/value type of comparison, then management can do their job and either buy in, or reject it. If not authorized to make a decision yourself, all that you can do (well, legitimately) is provide information to those that are. There may be a valid risk that you have not yet considered, or a benefit that they have not.

Good luck!

--MidLifeXis

[reply]