There is a new Pharo build available!
The status of the build #79 was: SUCCESS.
The Pull Request #2526 was integrated: "2525-DiskStoredelete-UTF8-encodes-twice"
Pull request url: https://github.com/pharo-project/pharo/pull/2526
Issue Url: https://pharo.fogbugz.com/f/cases/2525
Build Url:
There is a new Pharo build available!
The status of the build #78 was: FAILURE.
The Pull Request #2545 was integrated: "Bottom88"
Pull request url: https://github.com/pharo-project/pharo/pull/2545
Issue Url: https://pharo.fogbugz.com/f/cases/Bottom88
Build Url:
On 2/14/19 11:28 AM, Sven Van Caekenberghe wrote:
OK, where is the registry, how does it work, where can I read about it ?
`MetacelloProjectRegistration registry` ... It is a private registry of
loaded baselines and configurations used by Metacello. It's been around
roughly 6-7 years or so
> Le 14 févr. 2019 à 22:34, Sean P. DeNigris a écrit :
>
> demarey wrote
>> Probably because the email title is « can’t install launcher … » and the
>> issue only raises if you try to open Iceberg ;)
>
> Except Max said:
> I downloaded it again... and opened Iceberg without issues.
> !!
Good
demarey wrote
> Probably because the email title is « can’t install launcher … » and the
> issue only raises if you try to open Iceberg ;)
Except Max said:
I downloaded it again... and opened Iceberg without issues.
!!
-
Cheers,
Sean
--
Sent from:
Hi Sven,
https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md
includes a chapter on load conflicts.
Thx
T.
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
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.
> Le 14 févr. 2019 à 18:37, Sean P. DeNigris a écrit :
>
> demarey wrote
>> Here is a fix for it:
>> (IceRepository registeredRepositoryIncludingPackage: (RPackageOrganizer
>> default packageNamed: 'PharoLauncher-Core'))
>> name: 'pharo-launcher';
>> location: nil
>
> That worked!
> On 14 Feb 2019, at 18:40, Sean P. DeNigris 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
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
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…
-
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
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:
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:
Hi,
I noticed that some tests from XML Support started failing with the latest
version of Zinc. The 4 tests are XMLHTTP[Request|Response]>>#testAddHeader
#testHeaderValuesAdd
And yes, something changed recently (a couple of months ago) in Zinc:
ZnMultiValueDictionary>>#at:add: became
There is a new Pharo build available!
The status of the build #75 was: SUCCESS.
The Pull Request #2530 was integrated: "2373-Tonel test is failing"
Pull request url: https://github.com/pharo-project/pharo/pull/2530
Issue Url: https://pharo.fogbugz.com/f/cases/Pharo8.0
Build Url:
https://github.com/pharo-project/pharo-launcher/issues/311
> Le 14 févr. 2019 à 10:57, Christophe Demarey a
> écrit :
>
>>
>> Le 13 févr. 2019 à 19:23, Sean P. DeNigris a écrit :
>>
>> Max Leske wrote
>>> Nope. I downloaded launcher just 20 minutes ago on Mojave and am using
>>> it without
> Le 13 févr. 2019 à 19:23, Sean P. DeNigris a écrit :
>
> Max Leske wrote
>> Nope. I downloaded launcher just 20 minutes ago on Mojave and am using
>> it without problems.
>
> Weird. Nuked startup preferences folder just in case. fullPath modification
> didn't help.
>
>> Where did you
I downloaded it again, extracted it to /Applications, ran Pharo7-64bit
and opened Iceberg without issues. Launcher created the working
directory at ~/Documents/Pharo, which should be fine w.r.t. permissions.
I'm out of ideas...
On 13 Feb 2019, at 19:23, Sean P. DeNigris wrote:
Max Leske
20 matches
Mail list logo
