On Thu, Feb 16, 2012 at 9:18 AM, Roderich Schupp <roderich.sch...@googlemail.com> wrote: > On Thu, Feb 16, 2012 at 16:01, Markus Jansen <markus.jan...@ericsson.com> > wrote: >> The problems described below don't hurt that much for PAR building, but do >> cause lots of overcautious "uses" indications >> when trying to build a module dependency graph. > > Known problem. M:SD wans't meant to do detailed dependency analysis - > just make sure we pack anything that might be required.
The B::C and perlcc API which faces the similar problem has these two options, which you might want to adopt: -u force "use" of a package or module, if the walker does not find or too optimisticly deletes it. -U "unuse" skip including this module or package. Also all children are not implicltly added, only if used explictly. With these two user options aside from the logic and (not too heavy) heuristics in the walker the deps might too heavy but they work mostly. -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/
