Re: Ending Build.PL if there are missing modules

2012-02-05 Thread Adam Kennedy
If the goal is only to pick up versioned dependencies, I'm surprised we even need to bother with that. For M:I I've been thinking of just scanning all of script and lib for /^use Module::Name 1.23/ to determine requires, and all of t to find build_requires/test_requires. Anything loaded without a

Re: Ending Build.PL if there are missing modules

2012-02-05 Thread Adam Kennedy
That's how Module::Install's requires_from does it too. I should look at zilla's code and see how it runs, might be worth aligning M:I and it's detection. Adam On Sun, Feb 5, 2012 at 12:31 AM, David Golden wrote: > On Sat, Feb 4, 2012 at 7:48 AM, Leon Timmermans wrote: >> On Sat, Feb 4, 2012 a

Re: Ending Build.PL if there are missing modules

2012-02-05 Thread Adam Kennedy
I was thinking about dropping anything without a specific numberic version completely and requiring manual, because I figure the chances for misidentification is too high (whereas a number will only really be there after a human has put some specific thought into it). Adam On Sun, Feb 5, 2012 at

Re: Ending Build.PL if there are missing modules

2012-02-05 Thread David Golden
On Sun, Feb 5, 2012 at 1:15 AM, Eric Wilhelm wrote: >>It doesn't help with optional, dynamic prereqs so those have to be >>specified manually, but that's unavoidable I think. > > I've experimented with detecting those using my Devel::TraceDeps on the > running test suite.  It is possible to see th