Description and Installation Notes:
https://codeberg.org/39zde/euma
current version: 1.2.0
or look at the colors here:
https://39zde.codeberg.page/euma/@main/.codeberg/webpage/dist/index.html
or bash one liner:
```bash
curl --proto '=https' --tlsv1.2 -sSf https://codeberg.org/39zde/euma/raw/branch/main/derived/lib/inkscape/scripts/install.sh | bash
```
(!) Also check the source code before executing a random script in the command line
current version: 1.2.0
checksum: 5e4565fe932c3bec64e5d2586d881e3b9d2ca14a47a09c5e4bc14f8f8a97cf32 euma-1.2.0.inkscape.zip
Why is this a zip file? It contains multiple subfolders, and inside ... is 1 gpl file.
It basically was an attempt to get inkscape.org to recognize the GPG(1) "signature/checksum", which can be uploaded along with the other files. I read on this guide(2) to zip it and then sign it, so I gave it a try. But not matter what I tried, the website would not accept the signature and says it was broken. When checking it in the command line with the same GPG public key deposited In my account the signature was valid, so I guess the website is broken or I made an error. As a result the palette is now compressed. Since it does aid in reducing the transmission size I simply left it in place. Also, anyone wary of the zip file can just look at the linked repository. That's the story behind why there is a zip file with multiple sub-folders and only one gpl file inside.
(1) https://gnupg.org/
(2) https://inkscape.gitlab.io/extensions/documentation/authors/submit.html#i-want-to-submit-my-extension
I managed to get some sort of validation working, so here is what worked for me:
1. take the sha256sum of the file, which should be uploaded and store the hash in a file named the same as the upload-file with '.sha256' appended to the name
sha256sum $my_upload > $my_upload.sha256
2. upload the file
3. upload hash in the "signature/checksum" section
4. publish
Getting signing to work with gpg wasn't possible for me, so I'm documenting are my failed attempts to hopefully help others facing the same issues:
This is how inserted by gpg-public-key in my Inkscape account:
1. run this command
gpg --output public.gpg --armor --export $my_email
2. copy the contents and paste it into my Inkscape account
Here is what I tried and did not work:
- `gpg --sign-with $my-email --sign $my_upload` upload $my_upload with the signature $my_upload.gpg
- `gpg --sign-with $my-email --sign $my_upload` upload $my_upload with the signature $my_upload.sig
Ah, I see. Yes, it's a known issue. Website bugs are handled at https://gitlab.com/inkscape/inkscape-web