Hi,
Test results like
(http://www.cpantesters.org/cpan/report/07410474-b19f-3f77-b713-d32bba55d77f)
seem to indicate that the JOST smoker doesn't run the "install"
portion of the dependencies. It seems as if dependencies are only
built and then referred to by PERL5LIB to their blib/{arch,lib}.

I expected Judy.h to be installed to $Config{sitearch}/Alien/Judy but
it wasn't found though the dependency Alien::Judy was allegedly
installed. Given the below PERL5LIB, I think my Build.PL ought to
start looking in @INC for entries that look like blib/arch.

    PERL5LIB = 
/export/home/cpant3/.cpan/build/Alien-Judy-0.13-s5dqAk/blib/arch:/export/home/cpant3/.cpan/build/Alien-Judy-0.13-s5dqAk/blib/lib

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?

Josh

Reply via email to