# from Thomas Klausner
# on Monday 12 November 2007 12:05:
> check if all the modules used in a dist are also listed as a prereq
> ... by parsing Build.PL or Makefile.PL
How do you propose to address system-dependent requirements? (e.g. "$^O
eq 'MSWin32'" issues.) If you do not execute the Makefile.PL/Build.PL,
you do not know whether you are working from the correct list of
requisites.
>As you might know this is quite tricky, because some modules live in
>strange dists (e.g. HTTP::Request -> libwww-perl) and some modules are
> in Core (I'll check this with Module::CoreList).
And some modules spring into existence at compile time with
Package::Tent :-D
Are you planning to implement this with parsing or compiling the code?
I would love to see something like "run the test suite under
Devel::TraceLoad" and compare to the prereq list.
But that is probably a better author tool than a kwalitee metric,
especially if the kwalitee metric is wrong.
How about asking the author if they ran such a thing (e.g. checking
META.yml for a "yes, I did indeed run checkrequires before rolling this
dist" flag?)
In other words: how the metrics has_pod_test and has_pod_coverage_test
should have been done in the first place.
--Eric
--
Cult: A small, unpopular religion.
Religion: A large, popular cult.
-- Unknown
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
