What we envision if the following:
As a developer
you put the configurationOf in your project
Then if you want your package to be available in the
MetaCoolProjectsCatalogBrowser you should publish (special operation
which interprets the configuration recursively and copy all the needed packages
into the MetaCoolProjectsCatalogRepository of the current
version of pharo. So the configuration will be in both your project and the
distribution (because MetaCoolProjectsCatalogRepository is a disribution
of packages).
Now that metacello is available, we should push that because this is the way to
go.
One distribution per version and conifguration that can be tested automatically
by hudson.
Stef
