Re^2: All CPAN Modules

Well, Dave, I too favor choosing arbitrary data to illuminate a particular fact that my data set is incomplete on, mucho kudos :D (I'd have leaned higher in the order of 16.54% personally.)

however, I'm looking to build a build bot that will compile and install any and every module given, I already have a local mirror for the CPAN, I just want an easy way to install all the modules found. I realize, that OS and Arch specific modules won't build, I don't forsee much luck with Win32::API on a FreeBSD server, or getting that OS/2 File module to actually do anything on a Linux server. I guess anything that gives me a list of all the modules available on a CPAN mirror would be fine. I just need a list to iterate on is all.

Comment on Re^2: All CPAN Modules

Replies are listed 'Best First'.
Re^3: All CPAN Modules by Khen1950fx (Canon) on Apr 30, 2013 at 05:36 UTC
Rather than trying to install everything, it's better to break your list down into manageable chunks. For example to install all modules beginning with "A": `#!/usr/bin/perl use strict; use warnings; use CPAN; print $_->install() foreach CPAN::Shell->expand("Module", "/^A/");` [download] I usually break it down even further. For example, all modules starting with "Aa", "Ab", etc. `#!/usr/bin/perl use strict; use warnings; use CPAN; print $_->install() foreach CPAN::Shell->expand("Module", "/^Aa/"); print $_->install() foreach CPAN::Shell->expand("Module", "/^Ab/");` [download] And for an entire namespace, say Catalyst: `print $_->install() foreach CPAN::Shell->expand("Module", "/^Catalyst/");` [download]	[reply] [d/l] [select]
Re: All CPAN Modules by jnbek (Scribe) on Apr 30, 2013 at 05:43 UTC
Very nice!! Thanks these ideas will work very nicely.	[reply]
Re^3: All CPAN Modules by davido (Cardinal) on Apr 30, 2013 at 04:51 UTC
If you do craft a solution that iterates over "everything", there's probably some prior art to learn from by looking at how the CPAN smoke testers discover and test everything. You might want to pay particular attention to what the CPAN testers blocklist, because the most common reason for a smoker blocklisting a distribution is when they discover that the build process hangs nastily, or otherwise blocks forever. (I discovered that first hand when a mistake in one of my dists caused some smokers to hang.) Knowing which modules they consider impossible or too expensive to test will help you to avoid the same issues. Dave	[reply]