I was thinking in terms of Slime for Seaside. One PhD student is working on rule and I was thinking that it would be fun to have a kind of Metacello checker. do you have some rule of thumb where to look for potential problems? Because it can be a fun experience.
I had this idea of a checker for Metacello (that can be used with Versionner before committing), but never got the traction to do it. Some rules: - two packages in a graph of dependencies may rely on a different version of a third package - identifying cycles in packages - very important: checking whether the dependencies defined in Metacello matches with the actual source code. Said in other words, do I miss some dependencies in a configuration? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.