- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Preparing for release. No more PRs will be accepted on P7.
by Esteban Lorenzano Jan. 17, 2019

Jan. 17, 2019

Hi, > On 17 Jan 2019, at 20:19, Torsten Bergmann via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: "Torsten Bergmann" <astares(a)gmx.de> > Subject: Aw: [Pharo-dev] [ANN] Preparing for release. No more PRs will be accepted on P7. > Date: 17 January 2019 at 20:19:28 CET > To: pharo-dev(a)lists.pharo.org > Cc: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > > Hi Esteban, > > Good news that we get closer to a release. :) > > What is still the most annoying problem is that inbetween the build number had a hard reset during the switch to an "RC1" candidate > or after - so build numbers are currently at around "129" as you can see on the mails to the list. Yes, but we do not have a solution for this. Each branch has a different build number and is not possible to tweak it. > > The last shown by Pharo Launcher is 1436 builds with a Pharo 701436. > > This is not only confusing - but still breaks the launcher download. Or did I miss something? The download is broken not for that. Christophe is working in a new version of PL with that problem fixed. Cheers! Esteban > > Thanks > Torsten > >> Gesendet: Donnerstag, 17. Januar 2019 um 16:18 Uhr >> Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: [Pharo-dev] [ANN] Preparing for release. No more PRs will be accepted on P7. >> >> Unless is a show stopper, of course! >> >> Please redirect your PRs to the branch Pharo8.0. >> >> Esteban >> >> > > >

1 0

[ANN] Preparing for release. No more PRs will be accepted on P7.
by Esteban Lorenzano Jan. 17, 2019

Jan. 17, 2019

Unless is a show stopper, of course! Please redirect your PRs to the branch Pharo8.0. Esteban

2 1

[Pharo 8.0] Build #13: 2259-INVALID-ISSUE
by ci-pharo-ci-jenkins2＠inria.fr Jan. 17, 2019

Jan. 17, 2019

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

1 0

[Pharo 8.0] Build #12: 2193-SystemNavigation-should-use-Smalltalk-globals-but-environment-since-it-has-such-instance-variable
by ci-pharo-ci-jenkins2＠inria.fr Jan. 17, 2019

Jan. 17, 2019

There is a new Pharo build available! The status of the build #12 was: FAILURE. The Pull Request #2265 was integrated: "2193-SystemNavigation-should-use-Smalltalk-globals-but-environment-since-it-has-such-instance-variable" Pull request url: https://github.com/pharo-project/pharo/pull/2265 Issue Url: https://pharo.fogbugz.com/f/cases/2193 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #129: Fixes Issue #2256 Recover parameter names, remove unneeded temps in Character
by ci-pharo-ci-jenkins2＠inria.fr Jan. 17, 2019

Jan. 17, 2019

There is a new Pharo build available! The status of the build #129 was: SUCCESS. The Pull Request #2257 was integrated: "Fixes Issue #2256 Recover parameter names, remove unneeded temps in Character" Pull request url: https://github.com/pharo-project/pharo/pull/2257 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #128: 2254 leftover halts
by ci-pharo-ci-jenkins2＠inria.fr Jan. 17, 2019

Jan. 17, 2019

There is a new Pharo build available! The status of the build #128 was: FAILURE. The Pull Request #2255 was integrated: "2254 leftover halts" Pull request url: https://github.com/pharo-project/pharo/pull/2255 Issue Url: https://pharo.fogbugz.com/f/cases/2254 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] CMake
by Esteban Lorenzano Jan. 17, 2019

Jan. 17, 2019

Hi, Yes, when we had the CMake files, I used to generate an Xcode project to work on macOS. This was very good for work/debug. > On 17 Jan 2019, at 03:21, Ben Coman via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Ben Coman <btc(a)openinworld.com> > Subject: CMake > Date: 17 January 2019 at 03:21:18 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org>, Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On Thu, 17 Jan 2019 at 06:17, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > - About CMake, you may be right that makefile is better than CMake but a part of the world is using > CMake and the net result is that we lost our effort and infrastructure just to follow you. Ronie uses CMake. > Igor which I consider as a talented developer used CMake because he thought it was the best tool > he should use. > > Yes, and I disagree about the way that they use it, and for good reason. I have defended my use of Makefiles for a long time, for objective reasons. > > These reasons may be technically correct, but in terms of *community* consider it similar to premature optimization. > For yourself, the priority is a faster build. Others may prioritize a faster coding workflow using an IDE like Visual Studio. > Indeed, back when I trialed building minheadless on Windows a *primary* consideration was that it looked easy to > use Visual Studio because minheadless had a CMake build. That led to me contributing a couple of small fixes for win64, > but without the enticement of CMake I might never have opened that box. > > Consider then the possibility that a portion of our Windows using community remains untapped > because their skill set is Visual Studio and they don't see an easy path to using it with plain makefiles**. > So it depends on what is better for the *community* to optimize for: > * faster build-time for incumbents (important because thats where the majority of contributions come from) > * broader community involvement with a workflow accelerating IDE (important because growing the vm community is important, from which additional core devs may arise) > > ** I do understand that plain makefiles can be used with VS, but I'm not clear on the setup and > unsure if all the fancy intellisense tools work. > > I have also proposed good ways for using CMake (to derive a platform-specific header file defining available platform-specific features). > > I presume its the additional multi-build-system features that people want CMake for, not just the using it in name only. > I can't remember the trade-off between Automake-configure and CMake-configure. Make using CMake-configure > would make it easier to co-ordinate parallel CMake and GnuMake systems. I think I've noticed several large > code-bases providing both (but I'd have to check) > > > But my objection to Igor's process was that he generated sources on each build. > > > And my objections to Ronie's use of CMake for the minheadless build are that a) it is slow and > > I'd like to quantify that. > @esteban, I remember you converted minheadless from CMake to Gnumake, but I'm not sure if I've got that right. > Can both be run off the current HEAD for minheadless? Or I could compare HEAD with a previous commit that had CMake. I do not understand you question :) What is now in head should be the result of my(our, with Ronie) work. Esteban > > > b) explicit feature sets are much better than the implicit feature sets that arise when using CMake. > > I'd like to understand this better. Could you expand? > > cheers -ben > >

2 1

[Pharo 7.0] Build #127: 22897-Restore-getEnv-with-a-deprecation
by ci-pharo-ci-jenkins2＠inria.fr Jan. 17, 2019

Jan. 17, 2019

There is a new Pharo build available! The status of the build #127 was: FAILURE. The Pull Request #2252 was integrated: "22897-Restore-getEnv-with-a-deprecation" Pull request url: https://github.com/pharo-project/pharo/pull/2252 Issue Url: https://pharo.fogbugz.com/f/cases/22897 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Smalltalks 2018 videos are live
by Gabriel Cotelli Jan. 16, 2019

Jan. 16, 2019

Hi, We finished uploading all the videos of the conference. You can get the links and related info here <https://smalltalks2018.fast.org.ar/talks>. Regards, Gabriel in name of FAST

1 0

Looking for contributor names
by Esteban Lorenzano Jan. 16, 2019

Jan. 16, 2019

Hi, Is that time of the year (well, this time was more than one year) when I ask for the names of people who contributed to Pharo but didnât put their names. I thought this was going to be fixed with the move to GitHub, but seems that also there, there are people that does not use names :) So, Iâm missing this names: - vonbecmann - Karnaj - dupriezt - pierretsap - akevalion - Marmat21 If you are one of those, or you know the name of one of those, please tell me. Esteban Ps: Yes, that means we are very-very close of the release :)

3 3