Re: Ending Build.PL if there are missing modules

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 <[email protected]> wrote:
> On Sat, Feb 4, 2012 at 7:48 AM, Leon Timmermans <[email protected]> wrote:
>> On Sat, Feb 4, 2012 at 1:32 AM, Adam Kennedy
>> <[email protected]> wrote:
>>> While I agree it needs to finish, I do kind of wish dependencies could
>>> be enforced at the build module level so that tests couldn't run until
>>> dependencies are satisfied.
>>
>> I tend to agree with that. I've been writting Test::CheckDeps
>> (warning: very much a 0.001 release) to make it crap out as early as
>> possible during testing, but it could be even earlier.
>
> Plenty of code has dependencies listed that aren't truly required and
> tests will pass with lower versions.
>
> The proper way to enforce dependencies is in a "use" statement:
>
> =A0use Foo::Bar 1.23;
>
> Not coincidentally, that's how Dist::Zilla detects dependencies,
> ensuring that code and specified prereqs are actually in sync.
>
> In my view, other tools are doing it wrong.
>
> -- David