"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.

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

See A Guide to Installing Modules and A guide to installing modules for Win32 which are both in Tutorials.

I have in the past downloaded and installed a .ppd file that was not in the Active State Repository. That is rare for me and I haven't done it in some years. I have never built an AS module from "scratch". That is possible, however normally there is no need for this.

I did some googling and it is possible for you to make your own "ppm repository mirror" which you could put on a flash drive.

You might want to look at repository info, old but some info relevant.

I have no idea of the political environment at your workplace. If I were your manager, I would want that everything that you do be done in a maintainable process. If you need some module for your work, I would find a way to make that happen for you in an "official" way. If there is a reason for this that makes financial sense for the business, I would find a way. Consider the option of talking with your boss.

Things that would bolster your case: a) module has a long history, b) it is well maintained with regular updates, c)has few outstanding defect reports, d) will help me be more productive because of X. Get your "ammo" together before talking with the boss.

You may not understand that the Active State .ppd file has everything needed for the installation. It is pre-compiled and "ready to go" .

No, .ppd is just xml file that says whats available for download... .ppmx is a zip file containing a .ppd and one module distribution, see http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html#ppmx_files

Your link is similar as the one I posted. Good info about what files it needs! My machine is connected to the internet so this .ppd XML file worked. I would add that the XML .ppd file does contain the dependencies.

my link had:
http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html
your link has:
http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html#ppmx_files

fair enough.

Update: The reason that my downloaded .ppd files worked is that my machine can access the internet and I can "get the .ppd payload". I have successfully "cloned" an Active State installation from one machine to another by copying my main AS dir to the other machine with the same AS version (given a base installation of the same AS version). However, there is a lot that can go wrong with this idea. I do NOT recommend that idea. Certainly not in a corporate environment.

I forget the exact syntax right now, but there is a way to have AS dump a file with descriptions of "modules that need to be installed" and that can be used to "clone" your installation. This is the preferred way to "clone" an installation on another machine that doesn't violate any copyrights, etc. And you get the latest versions. I have successfully done that with another user before.