Re: Ending Build.PL if there are missing modules

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.

Adam

On 4 February 2012 10:22, Leon Timmermans <[email protected]> wrote:
> 2012/2/3 Alberto Sim=F5es <[email protected]>:
>> Hello
>>
>> Builder->new seems to check if all required modules are available. But i=
f
>> any fails, it continues to process the Build.PL file.
>>
>> Is there any way to make it stop?
>>
>> Thanks
>
> Hi Alberto,
>
> You shouldn't make it stop. =ABperl Build.PL=BB does configuration, not
> building. Hence build or runtime requirements are not required to be
> satisfied. What you're observing is not an error in any way, but an
> essential step in the process. It gives the install tool the chance to
> tell the cpan client (or the end user, if he's installing by hand) the
> opportunity what dependencies to install.
>
> If there are any missing dependencies, you'll notice it soon enough
> (in particular when doing =AB./Build test=BB.
>
> Leon