> On 19 Apr 2018, at 11:25, Gabriel Cotelli <g.cote...@gmail.com> wrote: > > And please support the use of baselines. Nobody wants to also mantain a > ConfigurationOf just for the catalog when using baselines.
that’s IMO the most important part we need to cover. Esteban > > On Thu, Apr 19, 2018, 05:58 Sven Van Caekenberghe <s...@stfx.eu > <mailto:s...@stfx.eu>> wrote: > I also think that the catalog is important. If anything is wrong with it we > should fix it. > > 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. > > 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. > > > On 19 Apr 2018, at 10:38, Torsten Bergmann <asta...@gmx.de > > <mailto: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 > >> <mailto:stepharo.s...@gmail.com>> > >> An: "Pharo Development List" <pharo-dev@lists.pharo.org > >> <mailto:pharo-dev@lists.pharo.org>> > >> Betreff: [Pharo-dev] Do we kill the catalog? > >> > >> Hi guys > >> > >> What do we do with it? > >> What alternatives? > >> > >> Stef > >> > >> > > > >
