> > Cargo is orthogonal to the need of a centralised repository. Yes, its idea is to provide one… but we will need a central repo, always.
Yes, but it already has STON manfiests to define the projects (project-metadata.ston). So why not use/extend the same file. Peter On Fri, Apr 20, 2018 at 7:23 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Thierry > > May be you are nervous these days. But try to relax and get a positive > mindset. > This is not perfect but it is there. You know that we are all full and > even more. > So just criticizing is not productive. > > > > One of the issues I have with the Catalog is that it made a mess of the > > various MetaRrepo for Pharo... Showing in the end that the single place > one > > should put a ConfigurationOf for Pharo is the squeak meta repo. > > If you find that funny it is not. > The point of having multiple repo was to make sure that contrary to > the old squeak experience > projects would load. > > > > That in addition the Catalog doesn't even use the best package > management we > > have at a given point is just salt rubbed in the wound. > > > I do not get what you mean but do not reply. > I do not think that it will be interested. You are in a ranting mode > and it deos not help. > > > > > > > As you wish. I know it belongs to one of these GUIs where I have to > spend 10 > > minutes to try to remember what the icons mean. But that's just me. > > Come on. There are fly by help > > > The key point to me is that the Catalog should reduce the friction it > > creates, not that the Catalog has to be a perfect solution. > > > > For example, do user-stories on it: how do one publish and updates a > project > > on the Catalog? What has one to do in CI to ensure a project is validated > > ... Can the catalog just takes care of that part, if the project has a > > correct setup (project has tests visible in the configurationOf, catalog > > does the CI stuff of testing it upon each new release of Pharo, even > stable > > because Iceberg breaks stuff when updated in Pharo 6.1, for example). > Tags > > for Pharo versions are only granted if project has been tested on CI by > the > > Catalog for the current version image you're in, for example. > > I have a long todo list too. We just did not get the resources for it. > Let us face it. > > > > We know how to explore and manipulate project specs already; look into > the > > GT tools for the code, and I also use a variant in my AltBrowser when I > sort > > all packages under the configuration or baseline they are specified in. > > > > In short, make it so that the Catalog is low friction and bring value to > > both project maintainers and users. > > > > Thierry > > > > > >> > >> Stef > >> > >> > >> On Thu, Apr 19, 2018 at 8:46 AM, Esteban Lorenzano <esteba...@gmail.com > > > >> wrote: > >>> > >>> why to kill it? > >>> right now we do not have a replacement. > >>> > >>> Esteban > >>> > >>>> On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.s...@gmail.com> > >>>> wrote: > >>>> > >>>> Hi guys > >>>> > >>>> What do we do with it? > >>>> What alternatives? > >>>> > >>>> Stef > >>>> > >>> > >>> > >> > >> > > > > > >
