On Wed, Dec 26, 2012 at 1:27 PM, Karen Etheridge via RT
<bug-CPAN-Reporter@rt.cpan.org> wrote:
Show quoted text> It would be extremely helpful to list the optional and recommended
> prereqs (as listed in the metadata), as well as the required ones, with
> failed test reports. Optional deps may be used in
> Test::Requires/eval/try_load_class blocks and their status can be
> relevant to deciphering a report.
It's a great idea, but would take a hefty rewrite of _prereq_report in
CPAN::Reporter.
The best way would probably be to detect MYMETA.json and pull all
prereqs from there with CPAN::Meta (if available). Otherwise, fall
back to the current approach that just takes prereqs that CPAN.pm
detected.
One tricky bit will be to merge prerequisites if they are different in
sections. (E.g. "requires Foo 1", "suggests Foo 1.2") The CPAN::Meta
dependencies like CPAN::Meta::Requirements should make that easy.
(All the CPAN::Reporter code predates such tools.)
Then it would have to be tested.
I don't have the tuits for it, but I'd be happy to provide pointers to
a volunteer. :-)
David
--
David Golden <dagolden@cpan.org>
Take back your inbox! →
http://www.bunchmail.com/
Twitter/IRC: @xdg
