Leandro Facchinetti

For reference: https://ubuntu.com/blog/snap-speed-improvements-with-new-compression-algorithm

Hmmm, that’s an interesting predicament. 1. Where did you get the Node.js you’re using to run caxa? 2. Did you try the Docker images [we’re using in our tests](https://github.com/leafac/caxa/blob/master/.github/workflows/main.yml#L116-L118) (or...

@maxb2: Did you run into this issue with the Raspberry Pi builds of Dungeon Revealer? How did you fix it?

If we can’t find a pre-compiled statically linked Node.js for ARM, then I guess the solution would be to come up with one ourselves. I believe that’s outside the scope...

Thanks for the information! On my laptop it took around 2 hours to compile Node.js. I suppose that we’d stay under the 6-hour time limit if we were to compile...

Yeah, that’s how I thought it’d turn out. I’ll keep the issue open for when someone steps up.

Y’all are doing some awesome work here. I love the hack to work around GitHub Actions time limits. You’re really pushing the envelope what the tool’s supposed to do. A...

Thank y’all for the amazing investigative work. I’m learning so much from you! It’s too bad that statically linked Node can’t load native modules… But I’m sure we’ll come up...

I’m happy to host and distribute some scripts with caxa for the packager’s convenience, but ultimately it’s their responsibility to make sure the scripts work for them—the scripts become part...

Of course, I believe that fixing this issue closer to the source would be ideal. Either by addressing https://github.com/nodejs/node/issues/37219 or by finding the right combination of options for compilation. Meanwhile,...