How to Build our Own Release? (Last release is a year old)

[CSEliot]

Hello,

The latest release is from 10 months ago yet the repo is still getting updates. There's no "build" instructions in the repo. A "Build" section in the README would be perfect.

Thanks!

[ORCHORDS]

Nothing here actually compiles, so "building your own release" is simpler than it sounds.

Look at what's in the repo: AffinityScripts/AffinityLinuxInstaller.py (the Python GUI installer), some legacy shell scripts, patches, docs. That's the whole product. The releases are just packaged snapshots of this — the AppImage in the latest release is a wrapper around the same installer flow, not a binary you'd produce with make/cargo/webpack.

Two ways to run the newest code:

Straight from a clone (always current):

git clone https://github.com/ryzendew/Linux-Affinity-Installer.git
cd Linux-Affinity-Installer
python3 AffinityScripts/AffinityLinuxInstaller.py

Same thing the README's curl one-liner does, minus the network fetch.

Fork + your own releases. Worth knowing first: .github/ in this repo contains only a FUNDING.yml — there's no Actions workflow producing the AppImage, so releases are manual uploads by the maintainer. That's why they lag behind commits. If you want fresh artifacts on your own schedule, you'd add a workflow on your fork that packages the installer on push (a trivial job for a Python + shell project) — and that same workflow would make a great PR here, since it fixes exactly the staleness you're seeing.

Your README "Build" section idea is the right call. Honestly the section would be three lines: clone, run the installer, optionally package with your CI of choice.