On Thu, Jun 10, 2010 at 3:44 PM, Vincent Pit <p...@profvince.com> wrote:
>
>> A possible change to my Build.PL is it'd start paying attention to
>> @INC and blib/arch to find possibly not-actually-installed files.
>>
>> --- a/Build.PL
>> +++ b/Build.PL
>> @@ -39,11 +39,23 @@ my $build = Module::Build->new(
>>
>>      create_readme => 1,
>>      dynamic_config => 1,
>> -    include_dirs => [ Alien::Judy::inc_dirs() ],
>> +    include_dirs => [
>> +        Alien::Judy::inc_dirs(),
>> +        (
>> +            map { File::Spec->catdir( $_, 'Alien', 'Judy' ) }
>> +            grep { m{blib/arch} }
>> +           �...@inc
>> +        ),
>> +    ],
>>
>> Is this actually reasonable or the right thing?
>>
> I believe the most reasonable approach would be to use
> ExtUtils::Depends, though I don't know how well it applies to the
> situation of an Alien:: module.

I try not to reach for EU::Depends because of the possibly related issue below:

I find it mildly annoying to use EU::Depends because of how it kicks
in the nuts "older" CPAN.pm libraries. Separately, I recently had to
learn to propagate a dependency up from a dependency. B::Utils
configure_requires ExtUtils::Depends and will exit(0) when it can't
continue. Some common/stock CPAN.pm I'd just built the other day
ignores that and doesn't stop recursive dependency resolution for
Data::Dump::Streamer. So now, the Makefile.PL for DDS has to check "if
I don't have B::Utils will it fail because we don't have EU::D" and
preemptively do an exit(0) itself to get the toolchain to behave.

Josh

Josh

Reply via email to