I think that's because local::lib manipulate PERL5LIB incorrectly. c.f. http://rt.cpan.org/Public/Bug/Display.html?id=66534
On Tue, Jun 21, 2011 at 10:58 AM, Chad Davis <chad.a.da...@gmail.com> wrote: > Agreed. That is one disadvantage. But I had more problems without > install=>1 such as this: > > https://rt.cpan.org/Public/Bug/Display.html?id=66549 > > It seems like a Module::Build issue, but not confirmed. I can still > test declaration of dependencies by temporarily hiding the smoker's > local::lib on a module-by-module basis, if needed. It's not a perfect > setup (I can't make it work with perlbrew), but it's smoother so far. > > > On Tue, Jun 21, 2011 at 16:41, Jeff Lavallee <j...@zeroclue.com> wrote: >> If you actually install modules, how do you identify modules that don't >> properly declare their dependencies? >> >> >> Jeff >> >> >> On Jun 21, 2011, at 6:45 AM, Chad Davis wrote: >> >>> I also found that relying on the build dir for finding dependencies, >>> rather than installing them, led to problems with various modules not >>> finding their dependencies. I now have CPAN::Reporter::Smoker install >>> everything, using a local::lib just for the smoker, so that it doesn't >>> conflict with anything else. >>> >>> source ~/setup-smoker-local-lib.sh; nice perl -MCPAN::Reporter::Smoker >>> -e "start(install=>1)" >>> >>> This has been working well for me. It seems to address the build_dir >>> problem as well as correctly finding dependencies. >>> >>> >>> >>> 2011/6/21 Serguei Trouchelle <s...@cpan.org>: >>>> Hello Daniel and CPAN Testers, >>>> >>>> I've found this very strange test result: >>>> http://www.cpantesters.org/cpan/report/048e04de-9b35-11e0-96f4-fdd92c767501 >>>> >>>> And after quick investigation found that there are also similar reports, >>>> and >>>> all of them have one similarity: an enormous PERL5LIB variable (more than >>>> 64k), which contains modules that totally unrelated to currently smoking >>>> package. >>>> >>>> So, if you use build_dir_reuse, PLEASE set clean_cache_after to some small >>>> value, and don't use default 100, because it's very likely to fill PERL5LIB >>>> to the point when unpredicted problems start to appear. Having something >>>> like Dist::Zilla::Some::Plugin smoked will definitely add *kilobytes* to >>>> PERL5LIB because of hundred of Moose dependencies (174 including core >>>> modules to be precise). >>>> >>>> -- >>>> Serguei Trouchelle >>>> >> >> >
