Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This would likely mean a lot of work for the maintainers to ensure that a module only went into the SDKs for which is applicable, but I think that could be automated once they got the hang of it

    As you say, this is a lot of work.

    I heard companies complaining about how not having this cost them a lot of money. But I don't see any of them lifting a finger to try to help solve it. If this truely is their itch, why are they not helping scratch it?

    (Yes, I am angry about companies that are effectively all take

    • I think perhaps the problem isn't as obvious to commercial organisations. Their developers learn how to make the fixes themselves rather than have a standard install they can upgrade. They don't escalate the problem.

      It's been a problem for me, as I want to do reliable cpan-testing, and unfortunately there are a growing number of distributions relying on specific versions of core modules.

      I do think this would be a nice task for someone new to an organisation, where by they can learn about core modules, dependencies and CPAN. It would give them good exposure some very relevant skills. Perhaps even a project on the Google's Summer of Code list for 2006 ;)