2018-04-19 10:57 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: > I also think that the catalog is important. If anything is wrong with it we > should fix it.
I agree. Issues: - The Catalog doesn't use Metacello, so things loaded via the catalog are not registered properly (upgrades / conflicts) - The Catalog mix multiple Meta repos and you never know, given a configuration in multiple repos, which one the Catalog is giving you. - The Catalog icons are ... non understandable. > The problem is that the catalog is never working well with the current > unstable version of Pharo (today 7). Not all package developers take the > trouble of checking/porting all the time, that is perfectly understandable. Never tried that one > Moving the catalog to GitHub with a STON meta description is a good idea, of > course. All we need is a clean object representing the meta info, the rest > comes for free. Maybe. I would like a automated way of extracting the json from a baseline or configuration... to reduce the friction of using the catalog. Thierry >> On 19 Apr 2018, at 10:38, Torsten Bergmann <asta...@gmx.de> wrote: >> >> Now today you had loading trouble with Smacc from Catalog ... and now >> directly want to >> kill catalog. Wow! >> >> Sometimes I have the impression that our community tries to reinvent itself >> each day >> doing it differently (but not only better) instead of extending, improving >> and supporting >> what we have have done before. Which sometimes is good ... but not always. >> >> Thx >> T. >> >>> Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr >>> Von: "Stephane Ducasse" <stepharo.s...@gmail.com> >>> An: "Pharo Development List" <pharo-dev@lists.pharo.org> >>> Betreff: [Pharo-dev] Do we kill the catalog? >>> >>> Hi guys >>> >>> What do we do with it? >>> What alternatives? >>> >>> Stef >>> >>> >> > >
