Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-18 Thread ducasse
Thanks Dave! Guille was taking care of OSSubprocess recently. I fixed bugs and issues last year. I do not think that mariano is looking at it. Stef > On 18 Mar 2019, at 03:19, David T. Lewis wrote: > > Hi Mariano, > > On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote:

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-17 Thread Ben Coman
On Mon, 18 Mar 2019 at 10:20, David T. Lewis wrote: > Hi Mariano, > > On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > > > ducasse wrote > > > > this is not because we do not care of Pharo that we will fix it > > > > immediately. > > > > > > Yes of course, just want

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-17 Thread David T. Lewis
Hi Mariano, On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > ducasse wrote > > > this is not because we do not care of Pharo that we will fix it > > > immediately. > > > > Yes of course, just want to keep it on the radar (and maybe Mariano will > > read he he) > > >

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-17 Thread Mariano Martinez Peck
> > > > > ducasse wrote > > this is not because we do not care of Pharo that we will fix it > > immediately. > > Yes of course, just want to keep it on the radar (and maybe Mariano will > read he he) > > I always do :) But honestly, I don't have enough time to carry on that myself. As you could

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-17 Thread ducasse
> ducasse wrote >> Our main problem is that >> - if more people would review PR >> - send PRs > > Thank you for the reminder of that bottleneck. I will try to do that more > now that we have moved to GH. The old process seemed too cumbersome to be > able to effectively utilize a few

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-16 Thread Sean P. DeNigris
ducasse wrote > Our main problem is that > - if more people would review PR > - send PRs Thank you for the reminder of that bottleneck. I will try to do that more now that we have moved to GH. The old process seemed too cumbersome to be able to effectively utilize a few free moments

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-15 Thread ducasse
Hi sean You see we are terribly busy working on a lot of cleaning in Spec. This is massive and this is super important for our roadmap. Guille and Pablo produce 600 tests. We are fixing duplication with Alain. Our main problem is that - if more people would review PR - send

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-15 Thread Sean P. DeNigris
Max Leske wrote >> I was talking about OSSubProcess > Well, I'm not working with that at the moment ;) [OT] Just want to bump the problem that OSProcess and OSSubProcess can't currently be used in the same image. This is an important problem because users can't control which library dependencies

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread Max Leske
On 14 Mar 2019, at 20:00, ducasse wrote: I was talking about OSSubProcess Well, I'm not working with that at the moment ;) On 14 Mar 2019, at 18:21, Tim Mackinnon wrote: I’ve been using OSProcess on OSX for exercism (development mode) and its been working fine. (I’ve been piping a go

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread Tim Mackinnon
Ohh - yeah, I can’t use that as it doesn’t support windows right? (It’s all a bit confusing) Tim Sent from my iPhone Sent from my iPhone > On 14 Mar 2019, at 19:00, ducasse wrote: > > I was talking about OSSubProcess

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread ducasse
I was talking about OSSubProcess > On 14 Mar 2019, at 18:21, Tim Mackinnon wrote: > > I’ve been using OSProcess on OSX for exercism (development mode) and its been > working fine. (I’ve been piping a go executable output to run a generation > command) > >> On 14 Mar 2019, at 16:38, ducasse

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread Tim Mackinnon
I’ve been using OSProcess on OSX for exercism (development mode) and its been working fine. (I’ve been piping a go executable output to run a generation command) > On 14 Mar 2019, at 16:38, ducasse wrote: > > > >> On 14 Mar 2019, at 17:33, Max Leske wrote: >> >> On 13 Mar 2019, at 11:55,

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread ducasse
> On 14 Mar 2019, at 17:33, Max Leske wrote: > > On 13 Mar 2019, at 11:55, ducasse wrote: > >> Ok now one of these days we will have to have all the important libraries >> hosted in the same place. >> It is not sure that we will maintain MC forever. >> For example SmalltalkHub should get

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-14 Thread Max Leske
On 13 Mar 2019, at 11:55, ducasse wrote: Ok now one of these days we will have to have all the important libraries hosted in the same place. It is not sure that we will maintain MC forever. For example SmalltalkHub should get readonly by the end of the year (for lack of maintenance reason).

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-13 Thread Max Leske
On 13 Mar 2019, at 11:55, ducasse wrote: Ok now one of these days we will have to have all the important libraries hosted in the same place. It is not sure that we will maintain MC forever. For example SmalltalkHub should get readonly by the end of the year (for lack of maintenance reason).

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-13 Thread ducasse
Ok now one of these days we will have to have all the important libraries hosted in the same place. It is not sure that we will maintain MC forever. For example SmalltalkHub should get readonly by the end of the year (for lack of maintenance reason). BTW is OSSubProcess working for you? > Hi

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-11 Thread Max Leske
Hi Stef, On 11 Mar 2019, at 8:12, ducasse wrote: Max ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit normal that it got removed in P7. But we should check this. I do not have the time today for this. normally ifNotNilDo: should be covered by a migrator automatic rewrite

Re: [Pharo-dev] OSProcess for Pharo 7

2019-03-11 Thread Thierry Goubier
Hi Max, use the following to load OSProcess: Metacello new configuration: 'OSProcess'; repository: 'http://www.squeaksource.com/MetacelloRepository'; load As I said a while ago, the ifNotNilDo: thing was corrected long ago and that configuration updated; the one in the catalog is