>>> >>> I strongly disagree. Metacello was sold to please users. Actually, I use it >>> for me, the developper. I create a new version at each commit. It works >>> wonderfully. >>> >> >> sorry, but if during development you need to do 2 commits of 20 >> packages , calculate how much time it would take for you to >> manuallly update a configuration for each update. >> it is time sink. >> >> if you do that once per day, its okay.. but for every commit . no. its >> is absurd. >> > unless there is an automated tool which can generate new configuration > automatically, hidden in your sleeve .. :)
there is a metacello browser that do that for you. Now I do not know if it handles subproject. The browser supports the process and use the MetacelloToolbox API. I should have a look when I will redo a complete pass on the metacello chapter. I wrote a memento so that we do not have to learn 35 pages to get all the details, but one page with the essential. Stef
