Makefiles: Packaging

[cookiengineer]

In order to get Stealth to work on the Pinephone, it's best to start with a PKGBUILD file for Stealth that can be used for Arch Linux users.

• [x] Setup package/ folder and a make.mjs.
• [x] make.mjs archlinux should create the final .tar.xz package.
• Setup a GitHub Action to build the package automatically. Not possible, as GitHub doesn't have archlinux as a runner OS.

[cookiengineer]

There's be two different packages:

tholian-stealth package:

• [x] Build a headless stealth package that requires only nodejs.
• [x] Integrate a systemd unit file
• [x] Build archlinux package file

tholian-browser package:

• [x] Build a GUI package that requires electron.
• [x] Integrate XDG .desktop file with app icon.
• [x] Build archlinux package file
• [x] Build electron-builder based package for MacOS
• [x] Build electron-builder based package for Windows

[cookiengineer]

As of https://github.com/tholian-network/stealth/commit/80d47b099e543679942d4161364cc2cd78494b3f this has been implemented.

The electron workflow for final app.asar package files is broken, though, as it requires a complete custom Filesystem implementation. Prefixed paths like file://, /app.asar/ etc won't work for anything that uses the native filesystem in the end (e.g. lstatSync() and others). Additionally, the app.asar file is temporarily mounted in completely different mechanisms on all platforms.

So, as of now, everything is packaged in an app.asar file, but the asarUnpack array in the electron builder config basically unpacks everything again - as it would be stupid to use webpack or another bundler just for the sake of embedding all assets inside the javascript runtime code.