NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Plagger dependencies (Score:2)
http://search.cpan.org/src/MIYAGAWA/Plagger-0.7.17/META.yml [cpan.org]
Plagger's "requirement" modules are all generic, from Cache, DateTime and LWP to HTML, XML and URI fetch modules. They are all necessary to all kinds of data sources and output as well. Other "plugins" are all pure perl and you can just skip installing the dependencies, which are disabled by default anyway for most plugins.
Believe me or not, I just replaced my work laptop with new MacBook a few weeks ago, and I installed Plagger and its dependencies with "notest" option of CPAN shell and by typing "n" (don't install) to most "recommended" dependencies, and it was so quick and easy, like done in 10 minutes with no failure at all.
Besides that, good work on Perlanet. You can steal options and filters from Plagger
Reply to This
Re: (Score:2)
You're absolutely right (of course!) The vast majority of the pre-requisites are optional. I had forgotten that.
I still think, however, that you're bundling too much stuff together. If I was bundling Plagger I'd create a core distribution that just read feeds, combined them and published new ones. I'd then relegate all
Re: (Score:2)
The only reason why we haven't done this was probably because we had never got to the point "yes we're done", and I just didn't want to see people uploading their random Plagger plugins to CPAN that will eventually be unmaintained, abandoned, out of sync with core, and in a poor quality code etc, etc.
It doesn't take you a minute to name a few Catalyst modules that are "out-of-date" or "was a total mistak