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.

My Perfect Cousin 3 Comments More | Login | Reply /

 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

    • Translating this to positive action points - if anyone reading this does want it, but doesn't have (free) time, can you make a business case to your employer to work on sorting out the problem as part of your job?

    • 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, dep

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.