On Oct 18, 2011, at 1:57 PM, Eric Wilhelm wrote: > # from Leon Timmermans > # on Tuesday 18 October 2011 00:37: > >> I've been pondering the same. For parts of the codebase that don't use >> much dynamic module loading it may be possible to automatize this >> using Perl::PrereqScanner. I think we could actually use some >> clustering algorithm after that (irony points for reusing biology >> knowledge there). > > If you have some tests, you may want to try running them through my > Devel::TraceDeps and getting a full runtime report of everything that > gets used. It might be useful before or after breaking the dist apart: > maybe you can determine your best groupings based on the tests. > > The output file contains enough info to map the hierarchy of require()s > in the 'trace' data, though I'm not sure if I've tried to put it into a > tree form. > > Also see the pdt-depcheck tool in the Devel-TraceDeps dist to verify > that your tests' dependencies match your Build.PL. > > --Eric
We have a general idea on how to split things up, but these suggestions will help a great deal. Thanks everyone! chris
