> Thats why I implemented a Configuration Browser which > is accessible from world menu "Tools" -> "ConfigurationBrowser".
Yes I know and I want it back :) > > It is a simple tool that should easy loading without all > these Gofer and install scripts. > > Its a simple tool - depending on Pharo version XX it points to > http://www.squeaksource.com/MetaRepoForPharoXX > and displays all ConfigurationOfXYZ within that repo. > > This worked in Pharo 1.2 and works in Pharo 1.3 also. > > By default in Pharo 1.3 it opens on > http://www.squeaksource.com/MetaRepoForPharo13 > - since this is empty and not filled by the community the browser > is unfortunately empty too. Yes for me this is the way to go!!! Because then we can have jenkins engine to build and validate the software for us. > > In Pharo 1.2 it showed some contents since I filled > http://www.squeaksource.com/MetaRepoForPharo12 > with copies of configs that are know to work with Pharo 1.2. > > > If you like you can (programmatically) open it on any > repository with configs you like: > > (MetacelloConfigurationBrowser new) > repository: 'http://www.squeaksource.com/MetacelloRepository'; > open > > So the idea is simple: if you have a ConfigurationOfSOMEPACKAGE > that is know to work in Pharo 1.3 then use the copy button of > Monticello browser to copy it to > http://www.squeaksource.com/MetaRepoForPharo13 > > So it is a simplified SqueakMap for Monticello configs. > > If you know Seaside is working than copy the mcz's of it's > config to > http://www.squeaksource.com/MetaRepoForPharo13 > and others can easily load it without evaluating scripts > in workspaces or search in repos. > > Unfortunately nobody cared to copy the configs. > Anything that has to happen is that the community copies > the config that are tested and that are known to work. > > My fault is that it looks like I missed to answer some > questions on [1] and [2] or to make it more clear what the > tool is all about. > > This simple tool will not solve the problem of porting packages > but may raise the visibility of packages that are known to > work in a Pharo version! Nothing more. But this is an important tool for me. Now we can just fill the repository with the right configurations and this should really support the idea of a real distribution. > Bye > T. > > [1] http://forum.world.st/Configuration-Browser-is-a-mastery-td3706003.html > [2] > http://stackoverflow.com/questions/6880596/how-to-browse-metacello-repositories-in-pharo-smalltalk
