Damien, Stef and I are going to talk at ESUG about the procedures/recommendations/tools for managing configurations in Pharo.
I (almost) apologize for naming the class MetacelloToolBox, but what do you expect from a person who makes up names all the time? With project names like Metacello or tODE and a blog called '(gem)Stone Soup' it's not always clear whether I'm making a mistake or a statement:) Dale ----- Original Message ----- | From: "Damien Pollet" <[email protected]> | To: [email protected] | Sent: Wednesday, August 17, 2011 12:56:10 AM | Subject: Re: [Pharo-project] Policy for storing metacello configurations | | On 17 August 2011 08:59, Max Leske <[email protected]> wrote: | > Some people seem to have adopted MetacelloRepository as the | > standard repository for all configurations, others keep the | > configuration for a project in the project repositories and a | > third group uses both repositories (where one repository contains | > outdated versions of course…). | | The MetacelloConfiguration belongs to the project and is under | responsibility of the developers, so one should be in the project's | repo. | | MetacelloRepository is the central well-known place, so maybe only | versions with a stable release really need to be there? | | There will be other well-known places, the idea is to have a curated | one for each version of Pharo I believe. | | In any case, maybe part of this should be docuplemented into | MetacelloToolBox ? | | (PS. toolbox is a proper english word, so that capital B in the class | name is unnecessary :) | -- | Damien Pollet | type less, do more [ | ] http://people.untyped.org/damien.pollet | |
