On Thu, Apr 14, 2011 at 11:21 PM, Markus Jansen <[email protected]> wrote:
> I have found that pp packs a lot of modules into the final application > which are definitely superfluous, but I don't have any clue where they get > referenced. No, they aren't superfluous in general, only in your context, but Module::ScanDeps can't know that. A simple example is File::Spec: it loads one of File::Spec::Unix, File::Spec::Cygwin, File::Spec::Win32 etc dynamically depending on the OS it runs on. Module::ScanDeps will include _all_ of them to err on the safe side. > I have the problem that I pack a rather large program with pp. > Apart from the usual quirks (adding modules and libraries manually), If you need to add a module (that lives on CPAN) explicitly that should be considered a bug in Module::ScanDeps. Please file a bug report in this case. > Is there any way to get a reference hierarchy a la Devel::TraceUse printed > out, > or let Module::ScanDeps somehow leak out debugging information? What do you miss in the data returned by Module::ScanDeps::scan_deps ? Cheers, Roderich
