Re: [Pharo-dev] Do we kill the catalog?

Just for the record https://pharo.fogbugz.com/f/cases/21825/Improve-Catalog-loading https://github.com/pharo-project/pharo/pull/1292 Feel free to review or to propose other PRs, Guille

Re: [Pharo-dev] Do we kill the catalog?

Thierry Goubier wrote > If using a baseline in the Catalog forces it to be more complex… I didn't think we were discussing changing baselines themselves, just a better adapter layer than hand-edited Configs Thierry Goubier wrote > A typical git-based development is one tag or branch per pharo >

Re: [Pharo-dev] Do we kill the catalog?

> Sent: Tuesday, April 24, 2018 at 3:42 AM > From: "Esteban Lorenzano" <esteba...@gmail.com> > To: "Pharo Development List" <pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] Do we kill the catalog? > > hi, > > > > On 24 Apr 20

Re: [Pharo-dev] Do we kill the catalog?

Hi Sean, Guille, 2018-04-24 15:31 GMT+02:00 Sean P. DeNigris : > Guillermo Polito wrote >> Should we continue providing configurations that point to the >> baselines? I've read some rants against it. >> I know it may be "uncomfortable", but publishing some meta-data in a >>

Re: [Pharo-dev] Do we kill the catalog?

Guillermo Polito wrote > Should we continue providing configurations that point to the > baselines? I've read some rants against it. > I know it may be "uncomfortable", but publishing some meta-data in a > repository in XXX technology is kind of the same... This seems like an implementation

Re: [Pharo-dev] Do we kill the catalog?

@lists.pharo.org >> Cc: "Pharo Development List" <pharo-dev@lists.pharo.org> >> Subject: Re: [Pharo-dev] Do we kill the catalog? >> >> Hi Stef, >> >> do not worry - I'm fully relaxed. It is you - who suggested to kill the >> catalog

Re: [Pharo-dev] Do we kill the catalog?

Hi all, I think that we are all aligned. Stef may be "too strong" in his way of talking, but he raised an issue: we should probably do an iteration on the catalog. And I think we all agree on that? So, what would be a list of tasks for it? (I copy past what Stef put before) - Use Metacello API.

Re: [Pharo-dev] Do we kill the catalog?

2018-04-24 7:31 GMT+02:00 Sven Van Caekenberghe : > > >> On 24 Apr 2018, at 00:49, monty wrote: >> >> +1. >> >> Replacing is sometimes necessary (Sven's stream work is an obvious example), >> but I don't see why Nautilus had to be junked rather than gradually

Re: [Pharo-dev] Do we kill the catalog?

aro-dev@lists.pharo.org >> Cc: "Pharo Development List" <pharo-dev@lists.pharo.org> >> Subject: Re: [Pharo-dev] Do we kill the catalog? >> >> Hi Stef, >> >> do not worry - I'm fully relaxed. It is you - who suggested to kill the >> catalog - without

Re: [Pharo-dev] Do we kill the catalog?

t 9:29 AM > From: "Torsten Bergmann" <asta...@gmx.de> > To: pharo-dev@lists.pharo.org > Cc: "Pharo Development List" <pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] Do we kill the catalog? > > Hi Stef, > > do not worry - I'm full

Re: [Pharo-dev] Do we kill the catalog?

Thierry Goubier wrote: >No +1 > > Just write that ston now for the current state of OSProcess (with all > versions and platforms supported). > > Or write that ston for a project that has stable branches for all pharo > versions, from say 1.3 to now. > > But, in

Re: [Pharo-dev] Do we kill the catalog?

n: "Stephane Ducasse" <stepharo.s...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.pharo.org> > Betreff: Re: [Pharo-dev] Do we kill the catalog? > > Torsten > > Sometimes you should relax. Because if you remember I pushed the > catalog (

Re: [Pharo-dev] Do we kill the catalog?

8 um 08:53 Uhr >> Von: "Stephane Ducasse" <stepharo.s...@gmail.com> >> An: "Pharo Development List" <pharo-dev@lists.pharo.org> >> Betreff: Re: [Pharo-dev] Do we kill the catalog? >> >> Hi torsten >> >> the wise shows the moon, th

Re: [Pharo-dev] Do we kill the catalog?

Even there is no learning from the past - it's deja vu all over again... > Gesendet: Freitag, 20. April 2018 um 08:53 Uhr > Von: "Stephane Ducasse" <stepharo.s...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.pharo.org> > Betreff: Re

Re: [Pharo-dev] Do we kill the catalog?

On sam. 21 avr. 2018 at 08:45, Stephane Ducasse wrote: > > the new name of Cargo > pakbot = paquebot in french = cargo in english :) Just for the record: https://github.com/demarey/cargo/issues/32 To explain the name change. > tx that you ask. > @Christophe what

Re: [Pharo-dev] Do we kill the catalog?

>> >> This is not for the others this is for US. >> And We plan to have a command line interface for the launcher and >> also for pakbot. > > > What is pakbot? the new name of Cargo pakbot = paquebot in french = cargo in english :) > > Let me know if we can join efforts, it would be sad to see

Re: [Pharo-dev] Do we kill the catalog?

El vie., 20 abr. 2018 4:39 p. m., Stephane Ducasse escribió: > > > > That's why I try to do with PI https://github.com/hernanmd/pi > > > > It's 100% command-line, which I know smalltalkers don't love. > > do not draw conclusions like that. > > > > However after working

Re: [Pharo-dev] Do we kill the catalog?

> > That's why I try to do with PI https://github.com/hernanmd/pi > > It's 100% command-line, which I know smalltalkers don't love. do not draw conclusions like that. > However after working with Python, R, Perl, etc. I saw the world > expects a pretty standard package installation pattern. > I

Re: [Pharo-dev] Do we kill the catalog?

On 20/04/2018 14:42, Hernán Morales Durand wrote: > Hi Stef, >> Do you think that editing STON is easier than a class? I think that we >> should have a button. >> Look people do not care about posting their project into the repo. >> May be we need a crawler? > That's why I try to do with PI

Re: [Pharo-dev] Do we kill the catalog?

Hi Stef, 2018-04-20 7:09 GMT+00:00 Stephane Ducasse : > The underlying questions (sorry for people that need subtitles) are: > > - how do we have a central place to declare projects > - right now in Smalltalkhub/list is a nice way to find projects > with the move to

Re: [Pharo-dev] Do we kill the catalog?

On Fri, Apr 20, 2018 at 7:28 PM, Peter Uhnák wrote: >> 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 >

Re: [Pharo-dev] Do we kill the catalog?

So what are the key "immediate" action to improve the situation - Support for Baseline (no idea what it means) - Use Metacello API. Metacello new repository: 'zzz' configurationOf: 'XXX' loadVersion: #'YYY' - What else? Stef On Fri, Apr 20, 2018 at 7:27 PM, Stephane Ducasse

Re: [Pharo-dev] Do we kill the catalog?

> > 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

Re: [Pharo-dev] Do we kill the catalog?

Hi guille should we open an issue and update the catalog? Stef On Fri, Apr 20, 2018 at 3:53 PM, Guillermo Polito wrote: > Hi all, > > IMHO, the problem is not metacello or gofer but the fact that the catalog > uses the old Metacello API: i.e., > > Gofer new >

Re: [Pharo-dev] Do we kill the catalog?

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

Re: [Pharo-dev] Do we kill the catalog?

On ven. 20 avr. 2018 at 15:53, Guillermo Polito wrote: > Hi all, > > IMHO, the problem is not metacello or gofer but the fact that the catalog > uses the old Metacello API: i.e., > > Gofer new > repository: 'zzz'; > configurationOf: 'XXX'; > load. >

Re: [Pharo-dev] Do we kill the catalog?

Hi all, IMHO, the problem is not metacello or gofer but the fact that the catalog uses the old Metacello API: i.e., Gofer new repository: 'zzz'; configurationOf: 'XXX'; load. (ConfigurationOfXXX project version: #YYY) load instead of the *new* Metacello API Metacello new repository:

Re: [Pharo-dev] Do we kill the catalog?

> On 20 Apr 2018, at 12:42, Cyril Ferlicot D. wrote: > > Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit : >> >> >>> On 20 Apr 2018, at 11:01, Thierry Goubier >> > wrote: >>> >>> Le 20/04/2018 à 09:09,

Re: [Pharo-dev] Do we kill the catalog?

> On 20 Apr 2018, at 12:20, Thierry Goubier wrote: > > Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit : >>> On 20 Apr 2018, at 11:01, Thierry Goubier >> > wrote: >>> >>> Le 20/04/2018 à 09:09, Stephane

Re: [Pharo-dev] Do we kill the catalog?

Thierry Goubier wrote > how do one publish and updates a project on the Catalog? What has one to > do in CI to ensure a project is validated To get started, it might be helpful to provide some snippets that people can insert into their own project's CI for this. I'll do a spike when I have a

Re: [Pharo-dev] Do we kill the catalog?

Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit : > > >> On 20 Apr 2018, at 11:01, Thierry Goubier > > wrote: >> >> Le 20/04/2018 à 09:09, Stephane Ducasse a écrit : >>> The underlying questions (sorry for people that need subtitles)

Re: [Pharo-dev] Do we kill the catalog?

Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit : On 20 Apr 2018, at 11:01, Thierry Goubier > wrote: Le 20/04/2018 à 09:09, Stephane Ducasse a écrit : The underlying questions (sorry for people that need subtitles) are: - how do

Re: [Pharo-dev] Do we kill the catalog?

> On 20 Apr 2018, at 11:01, Thierry Goubier wrote: > > Le 20/04/2018 à 09:09, Stephane Ducasse a écrit : >> The underlying questions (sorry for people that need subtitles) are: >> - how do we have a central place to declare projects >> - right now in

Re: [Pharo-dev] Do we kill the catalog?

hi, > On 20 Apr 2018, at 09:09, Stephane Ducasse wrote: > > The underlying questions (sorry for people that need subtitles) are: > > - how do we have a central place to declare projects >- right now in Smalltalkhub/list is a nice way to find projects > with the

Re: [Pharo-dev] Do we kill the catalog?

Le 20/04/2018 à 09:09, Stephane Ducasse a écrit : The underlying questions (sorry for people that need subtitles) are: - how do we have a central place to declare projects - right now in Smalltalkhub/list is a nice way to find projects with the move to github we should get a central

Re: [Pharo-dev] Do we kill the catalog?

The underlying questions (sorry for people that need subtitles) are: - how do we have a central place to declare projects - right now in Smalltalkhub/list is a nice way to find projects with the move to github we should get a central place Christophe has been working on project

Re: [Pharo-dev] Do we kill the catalog?

det: 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 >> >> >

Re: [Pharo-dev] Do we kill the catalog?

> What do we do with it? > What alternatives? > Stef Is Cargo dead? I thought that was supposed to be the alternative. > That sounds like a non-problem. One file that never needs to change. Let’s > solve the problems first > How so? If I want for the catalog to load a specific version of

Re: [Pharo-dev] Do we kill the catalog?

Gabriel Cotelli wrote: > And please support the use of baselines. Nobody wants to also mantain a > ConfigurationOf just for the catalog when using baselines. That sounds like a non-problem. One file that never needs to change. Let’s solve the problems first Stephan

Re: [Pharo-dev] Do we kill the catalog?

ore. 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>>

Re: [Pharo-dev] Do we kill the catalog?

t; > 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: &quo

Re: [Pharo-dev] Do we kill the catalog?

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...@g

Re: [Pharo-dev] Do we kill the catalog?

ting > 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-

Re: [Pharo-dev] Do we kill the catalog?

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: [Ph

Re: [Pharo-dev] Do we kill the catalog?

> > > > > Esteban > > > >> On 19 Apr 2018, at 08:42, Stephane Ducasse > wrote: > >> > >> Hi guys > >> > >> What do we do with it? > >> What alternatives? > >> > >> Stef > >> > > > On 19 April 2018 at 14:59, Esteban Lorenzano wrote: > > > > On 19

Re: [Pharo-dev] Do we kill the catalog?

> On 19 Apr 2018, at 08:46, Esteban Lorenzano wrote: > > why to kill it? > right now we do not have a replacement. btw, I had this idea of - using a STON spec instead a class (I think Dale has already something about it) - using github as centralised repository to

Re: [Pharo-dev] Do we kill the catalog?

why to kill it? right now we do not have a replacement. Esteban > On 19 Apr 2018, at 08:42, Stephane Ducasse wrote: > > Hi guys > > What do we do with it? > What alternatives? > > Stef >

[Pharo-dev] Do we kill the catalog?

Hi guys What do we do with it? What alternatives? Stef