Roderich Schupp via RT
2015-03-11 13:36:03 UTC
Wed Mar 11 09:36:01 2015: Request 102689 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Module::ScanDeps isn't effective
Broken in: (no value)
Severity: Wishlist
Owner: Nobody
Requestors: ***@cpan.org
Status: new
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=102689 >
Not that the above approach is also used by Module::ScanDeps if use
the --compile or --execute option. But the results only ADD dependencies
to the ones found during static analysis.
Cheers, Roderich
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Module::ScanDeps isn't effective
Broken in: (no value)
Severity: Wishlist
Owner: Nobody
Requestors: ***@cpan.org
Status: new
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=102689 >
Module::ScanDeps isn't effective.
You probably meant: efficient.Perl::LibExtractor produce much less deps tree.
It use different algorithm - "use package" in separate process and
parse %INC after - so only really used packages are found.
Also it works much more faster.
... but it doesn't catch all dependencies either.It use different algorithm - "use package" in separate process and
parse %INC after - so only really used packages are found.
Also it works much more faster.
Not that the above approach is also used by Module::ScanDeps if use
the --compile or --execute option. But the results only ADD dependencies
to the ones found during static analysis.
It will be useful to add possibility to use Perl::LibExtractor with pp
or use similar approach to build deps tree.
Code please - if you want to contribute some, add it to a wishlist bug for PAR::Packer.or use similar approach to build deps tree.
Cheers, Roderich