Re: Minimum CPAN modules you should count on?

perldoc perlmodlib lists what's core (i.e. what ships with perl itself). Past that you need to bug your sysadmin about integration with your OS' package managment software (see FreeBSD's bsdpan that makes CPAN modules appear as ports, for example) and read perldoc CPAN for information on the autobundle command.

Update: Also look at PAR for a mechanism for packaging up all your dependencies into a single file which will run regardless of what's installed on the other end.

Comment on Re: Minimum CPAN modules you should count on? Select or Download Code

Replies are listed 'Best First'.
Re^2: Minimum CPAN modules you should count on? by vek (Prior) on Jun 28, 2004 at 22:57 UTC
Yeah, I went the `PAR` route for deploying Perl apps on multiple Win32 desktops. The code I inherited had some rather yucky 'auto-install-if-the-module-is-missing' code tucked away in a `BEGIN` block. I don't remember exactly how the code went but it was something like this `BEGIN { eval { require FOO::Bar }; if ($@) { system("ppm install FOO::Bar"); } }` [download] PAR is by far the better way to go :-) -- vek --	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Minimum CPAN modules you should count on?
by vek (Prior) on Jun 28, 2004 at 22:57 UTC

Yeah, I went the PAR route for deploying Perl apps on multiple Win32 desktops. The code I inherited had some rather yucky 'auto-install-if-the-module-is-missing' code tucked away in a BEGIN block.

I don't remember exactly how the code went but it was something like this

BEGIN {
   eval { require FOO::Bar };
   if ($@) {
      system("ppm install FOO::Bar");
   }
}
[download]

PAR is by far the better way to go :-)

-- vek --

[reply]
[d/l]
[select]