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

[Pharo 7.0-dev] Build #142: 20459 Comment class ImportingResourceHelp

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

There is a new Pharo build available! The status of the build #142 was: SUCCESS. The Pull Request #305 was integrated: "20459 Comment class ImportingResourceHelp" Pull request url: https://github.com/pharo-project/pharo/pull/305 Issue Url: https://pharo.fogbugz.com/f/cases/20459 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 21, 2017

Re: [Pharo-dev] slow Pharo downloading and Travis

by Marcus Denker

> On 18 Sep 2017, at 08:37, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 16 Sep 2017, at 09:40, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi marcus >> >> I do not see why they could not find it. >> Can you tell me how you ask because we should reask? >> >> > > I spend a ticket and they wanted to close it last week. I have told them to not close it > The problems seems to be fixed now. If someone sees any slowness -> send me a mail. Marcus

Sept. 21, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

by Tudor Girba

Tough, indeed. But very exciting content. Doru > On Sep 20, 2017, at 10:22 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Yes it was the talk of the conference and it would have been a tough > talk without the cartoons :) > > On Wed, Sep 20, 2017 at 12:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> On 20 Sep 2017, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> More infos about Ring2: >>> >>> https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images >> >> The cartoons on the slides are hilarious ! >> >>>> On 20 Sep 2017, at 11:32, ci-pharo-ci-jenkins2(a)inria.fr wrote: >>>> >>>> There is a new Pharo build available! >>>> >>>> The status of the build #135 was: SUCCESS. >>>> >>>> The Pull Request #294 was integrated: "20434-use-Ring2-during-the-bootstrap" >>>> Pull request url: https://github.com/pharo-project/pharo/pull/294 >>>> >>>> Issue Url: https://pharo.fogbugz.com/f/cases/20434 >>>> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >>> >>> >> >> > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

Sept. 21, 2017

Contribution to the bootstrap process

by Pavel Krivanek

Hi, in relation to the issue https://pharo.fogbugz.com/f/cases/20447 Torsten asked me to describe how to prepare pull requests related to the bootstrap process. It is a little bit different from the standard pull requests because the code directory is different and the image needs to have some prerequisites loaded. 1) you need the current bootstrap image. This image contains the VMMaker, Espell, Beacon etc. You can find the latest path to it in the Jenkinsfile, now it is: https://github.com/guillep/PharoBootstrap/releases/download/v1.1.1/bootstra… You can prepare the image by yourself using the baseline in the repository https://github.com/guillep/PharoBootstrap. Currently we use Pharo 6 as the base system for it 2) place this image directly into your Pharo repository local clone folder 3) run the script bootstrap/scripts/prepare_image.st 4) open it and in Iceberg register your local clone as the local repository. In the path to the sources use "bootstrap/src" 5) continue as with a standard issue pull request, so create issue on FogBugz, create a branch, do your changes, commit them, pull them to your fork and create the pull request. For more information see: https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… Cheers, -- Pavel

Sept. 21, 2017

Re: [Pharo-dev] Iceberg Default Subdirectory Setting?

by stephan

On 21-09-17 03:40, Sean P. DeNigris wrote: > Stephan Eggermont-3 wrote >> Is that shared with multiple images? > > There is already a setting to share repos (actually to set a default repo > root folder). This setting would just be for where the packages live > relative to the git root folder of that particular repo (e.g. ./src, > ./repository, etc). Also, you'd still be able to alter it, I'm just talking > about the default value in the "Add local repo" dialog. I'm not quite sure how that share repos works. I normally have many images open that use different versions of shared repos. Git repos only have one current version. Stephan

Sept. 21, 2017

[Pharo 7.0-dev] Build #141: 20444 FFIExternalStructurePlatformTests cleanup (is32/64bit)

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

There is a new Pharo build available! The status of the build #141 was: SUCCESS. The Pull Request #301 was integrated: "20444 FFIExternalStructurePlatformTests cleanup (is32/64bit)" Pull request url: https://github.com/pharo-project/pharo/pull/301 Issue Url: https://pharo.fogbugz.com/f/cases/20444 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 21, 2017

[Pharo 7.0-dev] Build #140: 20446 Properly categorize finalizeValues and finalize messages in "finaliâ¦

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

There is a new Pharo build available! The status of the build #140 was: SUCCESS. The Pull Request #303 was integrated: "20446 Properly categorize finalizeValues and finalize messages in "finaliâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/303 Issue Url: https://pharo.fogbugz.com/f/cases/20446 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 21, 2017

[Pharo 7.0-dev] Build #139: 20458 Two uncommented classes in Reflectivity package

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

There is a new Pharo build available! The status of the build #139 was: SUCCESS. The Pull Request #304 was integrated: "20458 Two uncommented classes in Reflectivity package" Pull request url: https://github.com/pharo-project/pharo/pull/304 Issue Url: https://pharo.fogbugz.com/f/cases/20458 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 21, 2017

Re: [Pharo-dev] Iceberg Default Subdirectory Setting?

by Sean P. DeNigris

Stephan Eggermont-3 wrote > Is that shared with multiple images? There is already a setting to share repos (actually to set a default repo root folder). This setting would just be for where the packages live relative to the git root folder of that particular repo (e.g. ./src, ./repository, etc). Also, you'd still be able to alter it, I'm just talking about the default value in the "Add local repo" dialog. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 21, 2017

Re: [Pharo-dev] Iceberg Default Subdirectory Setting?

by Stephan Eggermont

On 20/09/17 23:50, Sean P. DeNigris wrote: > I always put my packages in gitroot/repository per instructions I read when I > was starting with FT (Dale's IIRC). It's a (minor) drag to type that every > time I add a local git repo. How would y'all feel about a setting? Is that shared with multiple images? How do you deal with needing different branches of the same repo? Stephan

Sept. 20, 2017