[Pharo-dev] How does Metacello decide what is already loaded ?
Sven Van Caekenberghe
sven at stfx.eu
Thu Feb 14 12:49:27 EST 2019
> On 14 Feb 2019, at 18:40, Sean P. DeNigris <sean at 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.
More information about the Pharo-dev