- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] gitfiletree on Windows

by Sebastian Sastre

yeah I don't even want to commit there just clone a repo so an image can be built there I guess I'm asking for too much from iPad > On 23/09/2014, at 09:49, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > > My short answer: despite trying for quite I while, I never succeeded and moved to FileTree only. > > Now, you can have a Windows VM under OS X where you share folders and images. > > Work wherever, run in Windows, commit on OSX. > > Frankenimages :-) > > Phil > >> On Tue, Sep 23, 2014 at 2:31 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> I'm taking a look at making gitfiletree in Windows and OSWindows seems to be helpful since OSProcess is no good for getting PipeableOSProcess executed in Windows. >> >> On the other hand, unless I'm missing something, there is no pipeable process in Windows so the whole strategy on how gitfiletree makes one command after the other changes (see gitCloneRepositoryAndCheckoutIn: aDirectoryName) >> >> Is anybody able to clone a git repo from a Pharo image in Windows? >> >> from iPad >

Sept. 23, 2014

Re: [Pharo-dev] IMPORTANT: new preLoad and postLoad process when making a fix

by Esteban Lorenzano

On 23 Sep 2014, at 13:50, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-09-23 13:29 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > This is a message for people doing fixes in Pharo core, and because of that doing SLICEs. > Since last week Iâm changing the integration process (something transparent for most of you), to make it more automatedâ¦ so I added two new fields to the issue tracker: > > - preload > - postload > > Soâ¦ from now, if your SLICE requires one or/and the other, you need to fill those fieldsâ¦ it will not be part of the comment fields anymore. > > thanks, > Esteban > > > Great! > > What if I want to do a "postload" only, > for example if we have an issue "need to reinitialize Class Xxxâ? the mail I sent says AND/ORâ¦ so that means you can express just one. Nowâ¦ If you put something like your example, instead putting Xxx initialize. then script will fail, because is a script, not a semantic analyser :) Esteban >

Sept. 23, 2014

Re: [Pharo-dev] IMPORTANT: new preLoad and postLoad process when making a fix

by Esteban Lorenzano

On 23 Sep 2014, at 13:37, Ben Coman <btc(a)openInWorld.com> wrote: > Esteban Lorenzano wrote: >> Hi, >> >> This is a message for people doing fixes in Pharo core, and because of that doing SLICEs. Since last week Iâm changing the integration process (something transparent for most of you), to make it more automatedâ¦ so I added two new fields to the issue tracker: >> - preload >> - postload >> >> Soâ¦ from now, if your SLICE requires one or/and the other, you need to fill those fieldsâ¦ it will not be part of the comment fields anymore. >> thanks, Esteban >> >> > > I've never used a preload or postload before in any way. Can you give an example? then you will not have a problem :) Some times you need to prepare something or clean up things (for example, is common when working with RPackage, that you need to re-scan the system). > cheers -ben > >

Sept. 23, 2014

Re: [Pharo-dev] gitfiletree on Windows

by phil＠highoctane.be

My short answer: despite trying for quite I while, I never succeeded and moved to FileTree only. Now, you can have a Windows VM under OS X where you share folders and images. Work wherever, run in Windows, commit on OSX. Frankenimages :-) Phil On Tue, Sep 23, 2014 at 2:31 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > I'm taking a look at making gitfiletree in Windows and OSWindows seems to > be helpful since OSProcess is no good for getting PipeableOSProcess > executed in Windows. > > On the other hand, unless I'm missing something, there is no pipeable > process in Windows so the whole strategy on how gitfiletree makes one > command after the other changes (see gitCloneRepositoryAndCheckoutIn: > aDirectoryName) > > Is anybody able to clone a git repo from a Pharo image in Windows? > > from iPad >

Sept. 23, 2014

Re: [Pharo-dev] Exceptions chapter of Deep Into Pharo

by Martin McClure

On 09/23/2014 12:40 AM, Christophe Demarey wrote: > Hello, > > Le 23 sept. 2014 Ã 04:36, Martin McClure a Ã©crit : > >> On 09/22/2014 09:43 AM, Damien Cassou wrote: >>> On Mon, Sep 22, 2014 at 4:44 PM, Martin McClure <martin(a)hand2mouse.com> wrote: >>>> OK, send me the SVN info and I'll work on the edits. >>> >>> >>> please create an account on https://gforge.inria.fr and ask to join >>> the project pharobooks. >>> >> >> Argh. I stupidly mis-typed my email address during account registration, so I'm "pending email confirmation" and the email will never be delivered. Any way to fix this or do I need to try again with a different login name? My login name is martinmcclure. > > You can ask the forge admins to fix your email address. > Send an email to help.et.gforge(a)inria.fr. Thank you, I have done this. Regards, -Martin

Sept. 23, 2014

gitfiletree on Windows

by Sebastian Sastre

I'm taking a look at making gitfiletree in Windows and OSWindows seems to be helpful since OSProcess is no good for getting PipeableOSProcess executed in Windows. On the other hand, unless I'm missing something, there is no pipeable process in Windows so the whole strategy on how gitfiletree makes one command after the other changes (see gitCloneRepositoryAndCheckoutIn: aDirectoryName) Is anybody able to clone a git repo from a Pharo image in Windows? from iPad

Sept. 23, 2014

Re: [Pharo-dev] can not compile pharo-vm on linux

by Damien Cassou

On Mon, Sep 22, 2014 at 11:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Did anything changed in the pharovm-linux-build-setup ? if you want a clean system where the pharo VM depends on libraries on your system and not on things downloaded at compile time, you can use these sources: http://files.pharo.org/vm/src/vm-unix-sources/blessed. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 23, 2014

Re: [Pharo-dev] IMPORTANT: new preLoad and postLoad process when making a fix

by Nicolai Hess

2014-09-23 13:29 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > This is a message for people doing fixes in Pharo core, and because of > that doing SLICEs. > Since last week Iâm changing the integration process (something > transparent for most of you), to make it more automatedâ¦ so I added two new > fields to the issue tracker: > > - preload > - postload > > Soâ¦ from now, if your SLICE requires one or/and the other, you need to > fill those fieldsâ¦ it will not be part of the comment fields anymore. > > thanks, > Esteban > Great! What if I want to do a "postload" only, for example if we have an issue "need to reinitialize Class Xxx"?

Sept. 23, 2014

Re: [Pharo-dev] IMPORTANT: new preLoad and postLoad process when making a fix

by Ben Coman

Esteban Lorenzano wrote: > Hi, > > This is a message for people doing fixes in Pharo core, and because of that doing SLICEs. > Since last week Iâm changing the integration process (something transparent for most of you), to make it more automatedâ¦ so I added two new fields to the issue tracker: > > - preload > - postload > > Soâ¦ from now, if your SLICE requires one or/and the other, you need to fill those fieldsâ¦ it will not be part of the comment fields anymore. > > thanks, > Esteban > > I've never used a preload or postload before in any way. Can you give an example? cheers -ben

Sept. 23, 2014

IMPORTANT: new preLoad and postLoad process when making a fix

by Esteban Lorenzano

Hi, This is a message for people doing fixes in Pharo core, and because of that doing SLICEs. Since last week Iâm changing the integration process (something transparent for most of you), to make it more automatedâ¦ so I added two new fields to the issue tracker: - preload - postload Soâ¦ from now, if your SLICE requires one or/and the other, you need to fill those fieldsâ¦ it will not be part of the comment fields anymore. thanks, Esteban

Sept. 23, 2014