> Am 17.05.2015 um 16:54 schrieb Pierce Ng <pie...@samadhiweb.com>: > > Hi all, > > When Torsten moved NBSQLite3 to PharoExtras on STH, he wrote a > ConfigurationOf, > which is in the PharoExtras/NBSQLite3 repository, and I have been updating > that. As it happens, in recent images, I used the configuration browser to > install NBSQLite3. After updating and committing the ConfigurationOf to > support > my latest changes to NBSQLite3, I see that the repository that was updated is > MetaRepoForPharo40. > > So now there exist on STH: > > #1 PharoExtras/NBSQLite3/ConfigurationOfNBSQLite3-PierceNg.9 > #2 Pharo/MetaRepoForPharo40/ConfigurationOfNBSQLite3-PierceNg.11 > > #2 is the updated one. > > What are the best practices to deal with this situation? Delete .9? (How?) > Configurations in a meta repo should never be updated directly. Usually a configuration lives in the project repo (here NBSQLite3). There it should be updated and maintained. Every now and then if there is a stable update it should be copied to the meta repo. The meta repo is also there to freeze the configuration so it will always be the same. Doing it like this it is natural to have an older configuration in MetaRepo30 an actual in MetaRepo40 and one in MetaRepo50.
Norbert
