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

Re: [Pharo-dev] Fwd: Where are the Metacello ConfigurationOfYourProject supposed to be?

by stepharong

Nicolas Since a couple of years already we have one MetaRepo per version MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo60' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo50' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo40' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo30' user: 'StephaneDucasse' password: '' You see it is in place since Pharo 30 :). We are working on a single place (web site) to publish packages but also the package metadata. The problem right now is that we cannot verify/publish a configuration without loading it. The idea is to have kind of distributions of packages working and validated vs. a folder full of possible packages I hated so much the squeak catalog because 5 times on 6 nothing worked. Stef

March 10, 2017

Pharo Association event listing updated

by Marcus Denker

Hi, I added all events (tech talks, sprints, pharodays) that will happen till June here: https://association.pharo.org/events Marcus

March 10, 2017

Re: [Pharo-dev] image not opening.

by Cyril Ferlicot D.

On 10/03/2017 15:27, Stephane Ducasse wrote: > Hi > > I have a jenkins that produce an image that does not start > when I try to open it locally. > > Now if I take the image and load the "same" configuration I get a > working image > > I have not idea how to debug that. > > Stef Hi, I have the same problem, only on the Pharo 6 builds. And sometimes it crash while launching the tests. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

March 10, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60438 Home: https://github.com/pharo-project/pharo-core

March 10, 2017

[pharo-project/pharo-core] d4cfeb: 60438

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d4cfebeac30af6f00482e1698b668bbeedf21530 https://github.com/pharo-project/pharo-core/commit/d4cfebeac30af6f00482e169… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-10 (Fri, 10 Mar 2017) Changed paths: R BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/preload_package_.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/baseline_.st M MonticelloFileTree-Core.package/MCFileTreeRepository.class/instance/storing/basicStoreVersion_.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/refresh.st A Ombu.package/OmDeferrer.class/instance/scheduling/runMessageProcess.st M Ombu.package/OmDeferrer.class/instance/scheduling/schedule.st M Polymorph-Widgets.package/UITheme.class/instance/morph creation/scrollBarDownButtonBoundsFor_.st R Refactoring-Critics.package/extension/ReAbstractRule/class/asRBRule.st R Refactoring-Critics.package/extension/ReAbstractRule/instance/asRBRule.st A Renraku.package/ReAbstractRule.class/class/conversion/asRBRule.st A Renraku.package/ReAbstractRule.class/instance/conversion/asRBRule.st A Renraku.package/ReAbstractRule.class/instance/testing/isComposite.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60437.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60438.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60437.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60438.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Tool-CriticBrowser.package/extension/ReAbstractRule/instance/isComposite.st Log Message: ----------- 60438 19786 MonticelloFileTree-Core package exported to Git contains a strange extension https://pharo.fogbugz.com/f/cases/19786 19825 circular dependency between Renraku and Refactoring-Critics https://pharo.fogbugz.com/f/cases/19825 19824 fix #scrollBarDownButtonBoundsFor: calculation https://pharo.fogbugz.com/f/cases/19824 19819 Epicea browser doesnt refresh when tests produce code changes https://pharo.fogbugz.com/f/cases/19819 http://files.pharo.org/image/60/60438.zip

March 10, 2017

image not opening.

by Stephane Ducasse

Hi I have a jenkins that produce an image that does not start when I try to open it locally. Now if I take the image and load the "same" configuration I get a working image I have not idea how to debug that. Stef

March 10, 2017

Re: [Pharo-dev] Fwd: Where are the Metacello ConfigurationOfYourProject supposed to be?

by Peter Uhnak

If you are looking for central repository, then Pharo Catalog is the closest thing to that. You copy your ConfigurationOf to the appropriate MetaRepoForPharo{40/50/60}. The ConfigurationOf can be just a copy of your actual ConfOf, or something that loads the actual one --- e.g. with Git you typically don't have ConfigurationOf, but BaselineOf (which doesn't contain any version information), and from the Catalog ones you just load this baseline. But considering git is only now gaining bigger traction it is in a flummox. Peter On Fri, Mar 10, 2017 at 01:04:59PM +0100, Sven Van Caekenberghe wrote: > > > On 10 Mar 2017, at 12:27, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > > > > > 2017-03-10 8:51 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > > On 10 Mar 2017, at 00:21, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > > > Grrr, even the mailing list changes, the first match in gmail just bounces, ;) > > > > > > ---------- Forwarded message ---------- > > > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > > > Date: 2017-03-10 0:05 GMT+01:00 > > > Subject: Where are the Metacello ConfigurationOfYourProject supposed to be? > > > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr>, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > > > > > > > > Hi, > > > I must come back to one of the balkanization and lack of stability that most upset me. > > > > > > Imagine that you are developping a cross dialect library, say for Squeak/Pharo and why not Gemstone. > > > > > > Imagine that this library has a few dependencies to some other libraries, either Core like Alien/FFI or more exotic third party also available in other dialects. > > > > > > The question are: > > > -1) where are you supposed to maintain your own ConfigurationOf*? > > > > Just next to your original source code. It is your config and you maintain it. > > > > > > Yes, I generally maintain the ConfigurationOf* in my own repo along with the other packages, > > and I copy the ConfigurationOf* to some centralized place (http://www.squeaksource.com/MetacelloRepository) > > It's like registering the application i nSqueakMap/CPAN/PyPI/etc... > > > > > > > -2) where are you supposed to find the ConfigurationOf* dependencies? > > > > Anywhere ;-) > > > > The config refers to its home repo. That is the one you should use in your dependency. > > > > OK, that's not particularly robust if source code repository is moving > > (i.e. on squeaksource, then ss3, then smalltalkhub, then github via filetree, then ...) > > > > A centralized Configuration provides a level of resilience. > > > > > > The different repos Pharo uses are for classification purposes. > > > > That is how I understand it anyway. > > > > > > No. The Pharos repos exist because we NEED something like a catalog (SqueakMap/CPAN/PyPI/whatever). > > Otherwise, ConfigurationOf* scattered around the web are not discoverable. > > > > The fact that there are as many repos as pharo versions is because there is no such easy thing as filtering the ConfigurationOf* matching target version without loading them all... > > > > Thanks Sven for answering. > > BTW, why do you continue to put copies in http://www.squeaksource.com/MetacelloRepository > > One single repo to rule them all is also a single point of failure, right ? > > As I understand it, the catalog (code/browser) searches backwards from its own version specific repo to all previous ones to the 'old' one you mention. > > Like I said, putting a config in a version specific repo means that you (or whoever makes the copy) acknowledge that you support that version or at least that it works there. It is a very soft, very simple mechanism. > > In the Pharo world, the catalog is the main entry point to easily loading stuff. But there is so much going on that that is certainly not the only way, nor is it possible to enforce just one way. There are teams that copy all source code repos and their configs to their own source code control systems to fix versions and to maintain absolute control and independence. YMMV. > > > Nicolas > > > > > Once upon a time, the answer would have been > > > http://www.squeaksource.com/MetacelloRepository > > > > > > But now, what is it? I see surprisingly few updates here (apart from Sven and a few others). > > > > > > How can the Metacello feature of supporting cross-dialect work if the dialect specific configuration of dependencies are scattered all around the web? > > > > > > Do the CPAN or PyPI have to change their URL each time a new release of perl or python is released? > > > > > > Careless decisions in this area can easily sabotage the cross-dialect initiative. > > > > > > Maybe I'm ranting by ignorance. > > > I wish your answers will reassure me. > > > > > > Nicolas > > > > >

March 10, 2017

Re: [Pharo-dev] Fwd: Where are the Metacello ConfigurationOfYourProject supposed to be?

by Sven Van Caekenberghe

> On 10 Mar 2017, at 12:27, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > 2017-03-10 8:51 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 10 Mar 2017, at 00:21, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > Grrr, even the mailing list changes, the first match in gmail just bounces, ;) > > > > ---------- Forwarded message ---------- > > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > > Date: 2017-03-10 0:05 GMT+01:00 > > Subject: Where are the Metacello ConfigurationOfYourProject supposed to be? > > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr>, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > > > > > Hi, > > I must come back to one of the balkanization and lack of stability that most upset me. > > > > Imagine that you are developping a cross dialect library, say for Squeak/Pharo and why not Gemstone. > > > > Imagine that this library has a few dependencies to some other libraries, either Core like Alien/FFI or more exotic third party also available in other dialects. > > > > The question are: > > -1) where are you supposed to maintain your own ConfigurationOf*? > > Just next to your original source code. It is your config and you maintain it. > > > Yes, I generally maintain the ConfigurationOf* in my own repo along with the other packages, > and I copy the ConfigurationOf* to some centralized place (http://www.squeaksource.com/MetacelloRepository) > It's like registering the application i nSqueakMap/CPAN/PyPI/etc... > > > > -2) where are you supposed to find the ConfigurationOf* dependencies? > > Anywhere ;-) > > The config refers to its home repo. That is the one you should use in your dependency. > > OK, that's not particularly robust if source code repository is moving > (i.e. on squeaksource, then ss3, then smalltalkhub, then github via filetree, then ...) > > A centralized Configuration provides a level of resilience. > > > The different repos Pharo uses are for classification purposes. > > That is how I understand it anyway. > > > No. The Pharos repos exist because we NEED something like a catalog (SqueakMap/CPAN/PyPI/whatever). > Otherwise, ConfigurationOf* scattered around the web are not discoverable. > > The fact that there are as many repos as pharo versions is because there is no such easy thing as filtering the ConfigurationOf* matching target version without loading them all... > > Thanks Sven for answering. > BTW, why do you continue to put copies in http://www.squeaksource.com/MetacelloRepository One single repo to rule them all is also a single point of failure, right ? As I understand it, the catalog (code/browser) searches backwards from its own version specific repo to all previous ones to the 'old' one you mention. Like I said, putting a config in a version specific repo means that you (or whoever makes the copy) acknowledge that you support that version or at least that it works there. It is a very soft, very simple mechanism. In the Pharo world, the catalog is the main entry point to easily loading stuff. But there is so much going on that that is certainly not the only way, nor is it possible to enforce just one way. There are teams that copy all source code repos and their configs to their own source code control systems to fix versions and to maintain absolute control and independence. YMMV. > Nicolas > > > Once upon a time, the answer would have been > > http://www.squeaksource.com/MetacelloRepository > > > > But now, what is it? I see surprisingly few updates here (apart from Sven and a few others). > > > > How can the Metacello feature of supporting cross-dialect work if the dialect specific configuration of dependencies are scattered all around the web? > > > > Do the CPAN or PyPI have to change their URL each time a new release of perl or python is released? > > > > Careless decisions in this area can easily sabotage the cross-dialect initiative. > > > > Maybe I'm ranting by ignorance. > > I wish your answers will reassure me. > > > > Nicolas > >

March 10, 2017

Re: [Pharo-dev] Fwd: Where are the Metacello ConfigurationOfYourProject supposed to be?

by Nicolas Cellier

2017-03-10 8:51 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 10 Mar 2017, at 00:21, Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com> wrote: > > > > Grrr, even the mailing list changes, the first match in gmail just > bounces, ;) > > > > ---------- Forwarded message ---------- > > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > > Date: 2017-03-10 0:05 GMT+01:00 > > Subject: Where are the Metacello ConfigurationOfYourProject supposed to > be? > > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr>, The > general-purpose Squeak developers list <squeak-dev@lists. > squeakfoundation.org> > > > > > > Hi, > > I must come back to one of the balkanization and lack of stability that > most upset me. > > > > Imagine that you are developping a cross dialect library, say for > Squeak/Pharo and why not Gemstone. > > > > Imagine that this library has a few dependencies to some other > libraries, either Core like Alien/FFI or more exotic third party also > available in other dialects. > > > > The question are: > > -1) where are you supposed to maintain your own ConfigurationOf*? > > Just next to your original source code. It is your config and you maintain > it. > > Yes, I generally maintain the ConfigurationOf* in my own repo along with the other packages, and I copy the ConfigurationOf* to some centralized place ( http://www.squeaksource.com/MetacelloRepository) It's like registering the application i nSqueakMap/CPAN/PyPI/etc... > > -2) where are you supposed to find the ConfigurationOf* dependencies? > > Anywhere ;-) > > The config refers to its home repo. That is the one you should use in your > dependency. > OK, that's not particularly robust if source code repository is moving (i.e. on squeaksource, then ss3, then smalltalkhub, then github via filetree, then ...) A centralized Configuration provides a level of resilience. > > The different repos Pharo uses are for classification purposes. > > That is how I understand it anyway. > > No. The Pharos repos exist because we NEED something like a catalog (SqueakMap/CPAN/PyPI/whatever). Otherwise, ConfigurationOf* scattered around the web are not discoverable. The fact that there are as many repos as pharo versions is because there is no such easy thing as filtering the ConfigurationOf* matching target version without loading them all... Thanks Sven for answering. BTW, why do you continue to put copies in http://www.squeaksource.com/ MetacelloRepository Nicolas > Once upon a time, the answer would have been > > http://www.squeaksource.com/MetacelloRepository > > > > But now, what is it? I see surprisingly few updates here (apart from > Sven and a few others). > > > > How can the Metacello feature of supporting cross-dialect work if the > dialect specific configuration of dependencies are scattered all around the > web? > > > > Do the CPAN or PyPI have to change their URL each time a new release of > perl or python is released? > > > > Careless decisions in this area can easily sabotage the cross-dialect > initiative. > > > > Maybe I'm ranting by ignorance. > > I wish your answers will reassure me. > > > > Nicolas > > > > >

March 10, 2017

Re: [Pharo-dev] Helvetia in Pharo?

by Serge Stinckwich

On Thu, Mar 2, 2017 at 8:51 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Helvetia requires a couple of things: BTW, with Nick Papoylias we have a working version of Helvetia for Pharo 5.0/Moose 6.0 here: https://github.com/UMMISCO/Helvetia We have the permissions of Lukas Renggli and Oscar Nierstrasz to port Helvetia to recent versions of Pharo. We are using Helvetia for our own research about Domain-Specific Languages for complex system especially in the context of the Kendrick DSL for epidemiology: https://ummisco.github.io/kendrick/ > - Flexible parsing. Lukas built PetitParser for this and now PetitParser2 is even faster and more powerful (for example, with bounded seas parsing) while preserving the same flexibility. > - Flexible compilation toolchain. At the time, Lukas employed a significant amount of overrides. Now we have Opal which makes this step easier. This has been the most difficult part of the port because the API change a lot since the PhD of Lukas :-) At the moment, the modifications that we have done are still a little bit hackish and more integration with Opal has to be done in the future. > - Moldable development tools. GT was designed with moldability in mind so at least the debugging part should be easier to handle. We still need work in the area of syntax highlighting, completion and editing. We will move soon the code on github so people could send pull requests. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 10, 2017