November 2017 - Pharo-dev - lists.pharo.org

STOP THE WORLD FINISHED

by Esteban Lorenzano

Hi, Yesterday we finish the conversion to tonel, but I announced it just replying to the build that realises it. So I announce here officially and in his own mail :) You can resume contributions. This change should improve everybody's life but in particular windows users. I would like to know how them feel the new format in that context. Of course, I know there are still a lot of optimisation/improvements we need to do, but this is a beginning :) cheers, Esteban

Nov. 3, 2017

Re: [Pharo-dev] [update 6.0] #60519

by Norbert Hartl

That is so cool. I think everyone that uses pharo in production appreciates this very much! Norbert > Am 03.11.2017 um 09:57 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > > >> On 3 Nov 2017, at 09:50, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Wow! Is there an explanation for that? If this is the pharo6 maintenance I would be very lucky! >> > > Yes, Pharo6 maintenance. The idea is to back port what makes sense and especially things that > people find and need fixed. > > E.g. Clement provided the FFIExternalStructure post load. > > Marcus > >> Too many good things happening here, too less time to spent! >> > > Far too many thingsâ¦ which is good :-) > > Marcus

Nov. 3, 2017

Re: [Pharo-dev] Tonel questions

by Stephane Ducasse

I went too fast I removed everything and reforked recloned :) let us if it is working. On Fri, Nov 3, 2017 at 9:49 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > 2017-11-03 9:39 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi >> >> >> Should I download the latest Pharo 7 image? >> Yes >> >> Should I fork again the Pharo-project? > > > no, just fetch and pull the latest version from the pharo-project/pharo > repository, the development branch. Then push it to your fork. >> >> >> Should I clone again the Pharo-project? > > > no, the step above does everything > > -- Pavel > >> >> >> Stef >> >

Nov. 3, 2017

Re: [Pharo-dev] [update 6.0] #60519

by Marcus Denker

> On 3 Nov 2017, at 09:50, Norbert Hartl <norbert(a)hartl.name> wrote: > > Wow! Is there an explanation for that? If this is the pharo6 maintenance I would be very lucky! > Yes, Pharo6 maintenance. The idea is to back port what makes sense and especially things that people find and need fixed. E.g. Clement provided the FFIExternalStructure post load. Marcus > Too many good things happening here, too less time to spent! > Far too many thingsâ¦ which is good :-) Marcus

Nov. 3, 2017

Re: [Pharo-dev] [update 6.0] #60519

by Norbert Hartl

Wow! Is there an explanation for that? If this is the pharo6 maintenance I would be very lucky! Too many good things happening here, too less time to spent! Norbert > Am 03.11.2017 um 09:46 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Super cool! > > > On Fri, Nov 3, 2017 at 9:43 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> In the build queue for Pharo6: >> >> 60519 >> ----- >> >> 20622 Pharo 6.1 Cannot use FFIExternalStructures out of the box >> https://pharo.fogbugz.com/f/cases/20622 >> >> 20611 leftover #logCr debug logging in GLEmptyBrick>>#area >> https://pharo.fogbugz.com/f/cases/20611 >>

Nov. 3, 2017

Re: [Pharo-dev] Tonel questions

by Pavel Krivanek

2017-11-03 9:39 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi > > > Should I download the latest Pharo 7 image? > Yes > > Should I fork again the Pharo-project? > no, just fetch and pull the latest version from the pharo-project/pharo repository, the development branch. Then push it to your fork. > > Should I clone again the Pharo-project? > no, the step above does everything -- Pavel > > Stef > >

Nov. 3, 2017

Re: [Pharo-dev] Tonel questions

by Cyril Ferlicot

On ven. 3 nov. 2017 at 09:40, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > > Should I download the latest Pharo 7 image? > Yes > > Should I fork again the Pharo-project? > > Should I clone again the Pharo-project? > > Stef > > Hi, You should get a new Pharo 7 image and sync your fork. Locally: git checkout development git pull [PHARO_REMOTE] development git push [FORK_REMOTE] development Then you are ready to go. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 3, 2017

Re: [Pharo-dev] [update 6.0] #60519

by Stephane Ducasse

Super cool! On Fri, Nov 3, 2017 at 9:43 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > In the build queue for Pharo6: > > 60519 > ----- > > 20622 Pharo 6.1 Cannot use FFIExternalStructures out of the box > https://pharo.fogbugz.com/f/cases/20622 > > 20611 leftover #logCr debug logging in GLEmptyBrick>>#area > https://pharo.fogbugz.com/f/cases/20611 >

Nov. 3, 2017

[update 6.0] #60519

by Marcus Denker

In the build queue for Pharo6: 60519 ----- 20622 Pharo 6.1 Cannot use FFIExternalStructures out of the box https://pharo.fogbugz.com/f/cases/20622 20611 leftover #logCr debug logging in GLEmptyBrick>>#area https://pharo.fogbugz.com/f/cases/20611

Nov. 3, 2017

[Pharo 7.0-dev] Build #252: 20626-Fixing-Tests-in-CI

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #252 was: SUCCESS. The Pull Request #425 was integrated: "20626-Fixing-Tests-in-CI" Pull request url: https://github.com/pharo-project/pharo/pull/425 Issue Url: https://pharo.fogbugz.com/f/cases/20626 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017