[Moose-dev] Can Moose help re-packaging code?

Hi Moose-List, up to version 2.8 Seaside was a huge monolithic package with a few extension packages. For Seaside 2.9 we try to split the whole code into smaller packages, to simplify deployment and porting. For example platform specific code should be in a separate package, and development tools, tests and examples should be loadable independently. We've coarsely split the code into multiple packages, however with all the code (around 500 classes and 5000 methods) it is difficult to see the dependencies and possible problems. I wonder if there is anything in Moose that could help us to get the package structure right? Visualize the dependencies of packages? Detect circular dependencies? Discover code that is placed in the wrong package? etc. I know that there is a package called MudPie for Squeak [1], that does something similar we want. Before trying to get it run I thought I ask here in the list for tips on how you would proceed with this endeavour. Happy new year, Lukas [1] http://map.squeak.org/package/617dbc24-e029-4d8c-a941-68db8c867952 -- Lukas Renggli http://www.lukas-renggli.ch