Hello,

The screenshot cuts off the error, but it may be the problem with file names that are too long in libgit2.

It's a controversial problem in libgit2 for at least six years.��https://github.com/libgit2/libgit2/issues/1899

Hitting this problem is what drove me to install WSL on Windows 10 and use Pharo that way, effectively not using Windows 10 for Pharo.

Other workarounds exist, including a short image name in the launcher, putting image folders at the root level, telling Pharo to put iceberg repos in a fixed directory closer to the root, etc. You want a way to prevent a Pharo file path that's longer than 260 chars.��

Cheers,

Cris

On Sun, Oct 6, 2019, 10:52 Shaping <shaping@uurda.org> wrote:

All you need to do is evaluating the following expression in a playground.

I suggest you do it in a fresh image.

��

Metacello new��
������baseline: 'PharoJS';
������repository: 'github://bouraqadi/PharoJS';
������load

��

That was one of the tests mentioned.���� See the screenshot below.�� The problem seems Git-related:

��

��

��

��

Shaping



On 6 Oct 2019, at 14:49, Shaping <shaping@uurda.org> wrote:

��

Hi.

Can someone explain exactly how to install the latest version of PharoJS,
and verify that the proedure really works?

I've tried:

1) cloning the PharoJS repo in Pharo 8.0 with Iceberg, and get a Not Loaded
final state for the repo.
2) loading into Pharo 7, 6.1, and 5 using

Metacello new
������baseline: 'PharoJS';
������repository: 'github://bouraqadi/PharoJS';
������load

All tries fail with a walkback.

3) loading into Pharo 4.0 using

Gofer it
smalltalkhubUser: 'noury' project: 'PharoJS';
addPackage: #ConfigurationOfPharoJS ;
loadStable.

The walkback here mentions missing dependency RBGlobalNode.


Suggestions are welcome. ��

Thanks.


Shaping





��