Nice!

• @Karolina-Bogacka could you test it on one of our Raspberries? That would be Linux ARM64. Please also do test it in WSL to make sure it works.
• @adanilenka can you test this on your Mac?
• @Karolina-Bogacka I feel like we should have a CI test for this. All of these platforms are supported by GH runners, so could we run this in CI?
• Does this support upgrades?
• Could we replace the URL to be https://w3id.org/jelly/setup-cli.sh? This will require extra magic in the w3id config – I can do that for you.

You decide what should be done in this PR and what in follow-ups coming shortly after.

Nice!

* @Karolina-Bogacka could you test it on one of our Raspberries? That would be Linux ARM64. Please also do test it in WSL to make sure it works.

* @adanilenka can you test this on your Mac?

* @Karolina-Bogacka I feel like we should have a CI test for this. All of these platforms are supported by GH runners, so could we run this in CI?

* Does this support upgrades?

* Could we replace the URL to be `https://w3id.org/jelly/setup-cli.sh`? This will require extra magic in the w3id config – I can do that for you.

You decide what should be done in this PR and what in follow-ups coming shortly after.

Apologies for the late reply. Tested on Ubuntu x86, on RPI (Linux ARM64), on Windows WSL on x86, and on Mac ARM64. Works on all of them, current behaviour shown in the image below.

The script right now by defaults overwrites any installation of jelly-cli that was already there, I made a separate issue for upgrades (#171), changing installation script URL (#172), and CI features (#170). The script adds the directory where jelly-cli to PATH by default and returns error messages if a given platform is unsupported.

You can try it out right now by running . <(curl -sSfL https://raw.githubusercontent.com/Jelly-RDF/cli/GH-32/prepare-an-installation-script/install.sh) if you'd like to check whether it works on your system