In Pharo 2.0 i started with Classes in one Package/Category (I'm not sure, what is the right term in Pharo at the moment). I have an identically named Monticello package which i contribute to.
Now i split the Package/Category:
becomes:
What is the intended way to manage these Packages/Categories with Monticello now? Is there a way to automatically split the Monticello packages accordingly? (I created some mess doing it manually and ended up starting in a new image and manually filing in the classes and then creating new Monticello packages)
I found this on the pharo developers mailinglist (splitting MC packages):
Closing the eyes and restarting from scratch. We did that too with the Seaside packages at some point. [...]
We did the same for Moose. We kind of followed this process:
- create new sub-package XYZ-Sub*
- move classes from XYZ to XYZ-Sub*
- repeat until all classes and extensions from XYZ are moved away to subpackages
- add the Monticello repository to XYZ-Sub*
- commit all XYZ-Sub* packages. Make sure that there are no categories without packages left behind (in other words to not lose code)
- save the image
- load in a fresh image
- if problems appear, and they always appear because it is manual work, go to the previous image and recommit