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
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
How this (c|sh)ould work... (Score:1)
1) Module authors list dependencies of their modules in Makefile.PL/Meta.yml (they already do, don't they?)
2) PAUSE parses this info and puts it into a cross-reference DB.
3) Authors can enter compatibility info into this DB via web interface, just saying "module M works with version X of module A and version Y of module B" or "module M doesn't work with version Z of module C". (could/should this be part of rt.cpan.org? I think so...)
3a) can also be augmented by cpan-tester-results?
4) CPAN publishes this x-ref list
5) cpan(p?) shell can download this x-ref list and finally present intelligent suggestions/questions to the user:
"by updating to version Z of module C you will break working module M. really proceed? N/y"
"you want to install module M that requires module A. do you want to install the latest version of module A (which may or may not work with module M) or better install version X of module A that is known to work?"
etc. etc. ad nauseam...
problem solved, now somebody go implement... *ggg*
Reply to This