index -|- my reference -|- full faq

from :

This is an excellent source of information ... hence the full local copy', as well as the link ;=))

This partial extract is some information about using cpan installer, in place of, or with, ppm ... if javascript is enabled, this page will automatically re-direct to the original full FAQ ...

Two Q & A that cropped up in my personal use of perl...
3.15. What if a module is not available in PPM format?
  Many of the CPAN modules are written entirely in Perl and don't require a compiler, so you can use the module/shell which comes with Perl. The only thing you need is nmake - a windows version of make which you can download from:

It's a self extracting archive so run it and move the resulting files into your windows (or winnt) directory.

Then go to a command window (DOS prompt) and run:

perl -MCPAN -e shell	

The first time you run the CPAN shell, you will be asked a number of questions by the automatic configuration process. Accepting the default is generally pretty safe. You'll be asked where various programs are on your system (eg: gzip, tar, ftp etc). Don't worry if you don't have them since will use the Compress::Zlib, Archive::Tar and Net::FTP modules if they are installed - and they are part of the ActiveState Perl distribution. Also don't worry if you make a mistake, you can repeat the configuration process at any time by typing this command at the 'cpan>' prompt:

o conf init	

If you're behind a firewall, when you're asked for an FTP or HTTP proxy enter it's URL like this:


You can probably use http:// for both FTP and HTTP (depending on your proxy).

After you've selected a CPAN archive near you, you will finally get a 'cpan>' prompt. Then you can type:

install XML::SAX

and sit back while downloads, unpacks, tests and installs all the relevant code in all the right places.

3.16. "could not find ParserDetails.ini"
  A number of people have reported encountering the error "could not find ParserDetails.ini in ..." when installing or attempting to use XML::SAX. ParserDetails.ini is used by XML::SAX::ParserFactory to determine which SAX parser modules are installed. It should be created by the XML::SAX installation script and should be updated automatically by the install script for each SAX parser module.
  • If you are installing XML::SAX manually you must run Makefile.PL. Unpacking the tarball and copying the files into your Perl lib directory will not work.
  • During the initial installation, if you are asked whether ParserDetails.ini should be updated, always say yes. If you say no, the file will not be created.
  • If you are using ActivePerl, the following command should resolve the problem:
    ppm install	

Once you have successfully installed XML::SAX, you should consider installing a module such as XML::SAX::Expat or XML::LibXML to replace the slower pure-Perl parser bundled with SAX.

If you are packaging XML::SAX in an alternative distribution format (such as RPM), your post-install script should check if ParserDetails.ini exists and if it doesn't, run this command:

perl -MXML::SAX -e "XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()" 

Don't unconditionally run this command, or users who re-install XML::SAX may find that any fast SAX parser they have installed will be replaced as the default by the pure-Perl parser.

index -|- my reference -|- full faq