Updating perl cpan Oschai with girlfriend

To run the CPAN shell, h Display Information command argument description a,b,d,m WORD or /REGEXP/ about authors, bundles, distributions, modules i WORD or /REGEXP/ about anything of above r NONE reinstall recommendations ls AUTHOR about files in the author's directory Download, Test, Make, Install...get download make make (implies get) test MODULES, make test (implies make) install DISTS, BUNDLES make install (implies test) clean make clean look open subshell in these dists' directories readme display these dists' README files Other h,? perl-code eval a perl command o conf [opt] set and query options q quit the cpan shell reload cpan load again reload index load newer indices autobundle Snapshot force cmd unconditionally do cmdcpan If it gripes about not having the proper header files, perhaps you don't have the header files for a higher level module.

updating perl cpan-66

For more advanced installation process, please read the perlbrew document.perlbrew is a tool to manage multiple perl installations in your While the default is good enough, you may customize it to install to alternative places, or even let multiple users share the whole perlbrew environment.To install the latest stable release, and use it permanently: perlbrew has always been improving, it is an open source project for everyone to participate.The Perl that comes stock on your Linux distribution or your Windows install is hugely powerful, but in fact it just scratches the surface.Throughout the years, people have created Perl modules to accomplish very specific tasks so that you don't need to rewrite the wheel to perform those same tasks.

But these modules are not, by default, on your computer. Often you can simply download the Perl code comprising the new module, and place that Perl code in the right place. When working with Linux, you can actually use Perl itself to download, make, test and install new modules. Downloading and installing new modules can be done entirely from within the Perl CPAN shell.

Working within the CPAN shell always triggers a compile, which can be good or bad, depending on the situation.

Obviously, if you have no C compiler (on a stock Windows box, for instance) or your C compiler is incompatible with the Perl modules, compiling is a bad thing.

In cases where the new module is entirely Perl code, you'd be better downloading the module and manually placing it in the proper part of the Perl module tree.

Also, compiling can take significant time, so you might want to go the straight Perl route. Source and object files take significant space, so if your /usr tree is almost full, you might want to stay away from compiles.

However, on fully compatible machines (Linux), using the CPAN shell with compiles is often the simplest route, and incorporates all features requiring recompilation.