# from Jason Forkey # on Friday 13 April 2007 01:41 pm: > Log::Log4perl actually depends on modules that >aren't pure perl, including ironically Compress::Zlib.
Module::ScanDeps makes some assumptions about which Log::Log4perl backends you want (basically, I think it assumes you want every Log::Log4perl::* module that's on the machine.) This can balloon the deps (including IIRC, DBI.) You might try running your actual code (test suite?) with chromatic's Devel::TraceUse (or my not-quite-out-of-alpha Devel::TraceDeps which is derived from that.) http://scratchcomputing.com/svn/Devel-TraceDeps/trunk ATM, you have to just grep/sed stderr to get anything useful from that, but it might be at least informative. Patches welcome. The dotReader par uses Module::ScanDeps and then manually blacklists some modules to avoid that specific Log::Log4perl exuberancy. The plan with Devel::TraceDeps is to plug it into the dotReader test suite and build an exhaustive run-time dependency map, then build the par from that with no build-time scanning. Anyway, deadlines... --Eric -- Speak softly and carry a big carrot. --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
