On 30 mars 2010, at 10:40, Tudor Girba wrote: I think the problem is that ConfigurationOfMoose plays two roles: managing the common parts of Moose and defining the Moose suite as common parts + projects. Maybe we should make this distinction clear with a ConfigurationOfMoose and ConfigurationOfMooseSuite? -- Simon

On 30 mars 2010, at 13:15, Tudor Girba wrote: Well, if one produces a new version of Moose suite, one should check that he is using compatible versions from MooseCore and SmallDude. That is, if you want to make a version of MooseSuite4.0 using MooseCore4.0.1 and Smalldude2.0.3, I think it's good practice to check that Smalldude2.0.3 also uses MooseCore4.0.1. I agree that the problem is not solved, it is just merely passed upon the level of versions instead of packages (but maybe it is easier to notice/check such problems at version level). BTW, I think that given two versions of a package, Metacello resolves to load the latest one right? My current problem is that I am trying to build the tree of dirty packages recursively through projects, but if a package belongs to two projects, it's not clear what to do with this package. -- Simon