February 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Torsten Bergmann

Hi Sven, https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… includes a chapter on load conflicts. Thx T.

Feb. 14, 2019

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Sven Van Caekenberghe

OK, where is the registry, how does it work, where can I read about it ? Let's make this more concrete: I load Bootstrap which will load Seaside and I load Material Design Lite which will load Seaside. Will Seaside be loaded twice ? On what does this depend ? How can we as a community make sure we are talking about the same Seaside ? That is essentially my question. I know it is not an easy question, but I find it an important one. > On 14 Feb 2019, at 20:09, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > As Sean said, when using Metacello scripting, it uses a registry, and > that's how it achieves the version "lock", "use local" or "use > incoming" version. > > And yes... there are a lot of things that "just work", we thank it, > take for granted, and complain when they fail :) > > Regards, > > Esteban A. Maringolo > > El jue., 14 feb. 2019 a las 14:50, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: >> >> >> >>> On 14 Feb 2019, at 18:40, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> >>> Sven Van Caekenberghe-2 wrote >>>> How does Metacello decide what is already loaded ? >>> >>> IIRC, if you load via the scripting API (i.e. 'Metacello new..."), versions >>> are kept in a registry, but if you use e.g. Gofer, it "guesses" the version >>> based on the package versions present. I can't answer your more specific >>> questions, but since one can "lock" based e.g. on repository location, that >>> must be considered somewhere. Also, NB, I doubt Dale actively follows this >>> list, so you may want to ping him. >> >> But is it not a bit sad that we don't know ? >> >> We're using it all the time, but we lack important information. >> >> This is probably because somehow Metacello does the right thing automagically, but still. >

Feb. 14, 2019

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Esteban Maringolo

As Sean said, when using Metacello scripting, it uses a registry, and that's how it achieves the version "lock", "use local" or "use incoming" version. And yes... there are a lot of things that "just work", we thank it, take for granted, and complain when they fail :) Regards, Esteban A. Maringolo El jue., 14 feb. 2019 a las 14:50, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > > > > On 14 Feb 2019, at 18:40, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > > Sven Van Caekenberghe-2 wrote > >> How does Metacello decide what is already loaded ? > > > > IIRC, if you load via the scripting API (i.e. 'Metacello new..."), versions > > are kept in a registry, but if you use e.g. Gofer, it "guesses" the version > > based on the package versions present. I can't answer your more specific > > questions, but since one can "lock" based e.g. on repository location, that > > must be considered somewhere. Also, NB, I doubt Dale actively follows this > > list, so you may want to ping him. > > But is it not a bit sad that we don't know ? > > We're using it all the time, but we lack important information. > > This is probably because somehow Metacello does the right thing automagically, but still.

Feb. 14, 2019

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

by Christophe Demarey

> Le 14 fÃ©vr. 2019 Ã 18:37, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > demarey wrote >> Here is a fix for it: >> (IceRepository registeredRepositoryIncludingPackage: (RPackageOrganizer >> default packageNamed: 'PharoLauncher-Core')) >> name: 'pharo-launcher'; >> location: nil > > That worked! Thanks. I wonder why Max did not get the error, thoughâ¦ Probably because the email title is Â« canât install launcher â¦ Â» and the issue only raises if you try to open Iceberg ;)

Feb. 14, 2019

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Sven Van Caekenberghe

> On 14 Feb 2019, at 18:40, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> How does Metacello decide what is already loaded ? > > IIRC, if you load via the scripting API (i.e. 'Metacello new..."), versions > are kept in a registry, but if you use e.g. Gofer, it "guesses" the version > based on the package versions present. I can't answer your more specific > questions, but since one can "lock" based e.g. on repository location, that > must be considered somewhere. Also, NB, I doubt Dale actively follows this > list, so you may want to ping him. But is it not a bit sad that we don't know ? We're using it all the time, but we lack important information. This is probably because somehow Metacello does the right thing automagically, but still.

Feb. 14, 2019

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > How does Metacello decide what is already loaded ? IIRC, if you load via the scripting API (i.e. 'Metacello new..."), versions are kept in a registry, but if you use e.g. Gofer, it "guesses" the version based on the package versions present. I can't answer your more specific questions, but since one can "lock" based e.g. on repository location, that must be considered somewhere. Also, NB, I doubt Dale actively follows this list, so you may want to ping him. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 14, 2019

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

by Sean P. DeNigris

demarey wrote > Here is a fix for it: > (IceRepository registeredRepositoryIncludingPackage: (RPackageOrganizer > default packageNamed: 'PharoLauncher-Core')) > name: 'pharo-launcher'; > location: nil That worked! Thanks. I wonder why Max did not get the error, thoughâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 14, 2019

How does Metacello decide what is already loaded ?

by Sven Van Caekenberghe

Hi, How does Metacello decide what is already loaded ? Specifically in the context of 'shared dependencies' ? Say project A depends on X and project B also depends on X ? How does Metacello then decide they are talking about the same X ? Is that by name only ? Does the repository count as well ? Does the version/group count ? How can I see what is known as loaded and what the dependencies are ? How can we, as a community, make sure that we properly share dependencies ? Sven

Feb. 14, 2019

[Pharo 8.0] Build #77: 2531-Removing-global-action-Introduce-DisplayableObject-

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

There is a new Pharo build available! The status of the build #77 was: FAILURE. The Pull Request #2533 was integrated: "2531-Removing-global-action-Introduce-DisplayableObject-" Pull request url: https://github.com/pharo-project/pharo/pull/2533 Issue Url: https://pharo.fogbugz.com/f/cases/2531 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 14, 2019

[Pharo 8.0] Build #76: 2529-MenuRegistration-MenuSpec-tag-should-be-merged-into-Core

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

There is a new Pharo build available! The status of the build #76 was: SUCCESS. The Pull Request #2532 was integrated: "2529-MenuRegistration-MenuSpec-tag-should-be-merged-into-Core" Pull request url: https://github.com/pharo-project/pharo/pull/2532 Issue Url: https://pharo.fogbugz.com/f/cases/2529 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 14, 2019