Plan builds and releases #2

New Issue

cassowary · 2023-12-02T20:15:18+01:00

cassowary commented

2023-12-02 20:15:18 +01:00

Even though we fork the upstream development version, we should think about how we can get PIKA into the hands of actual users (even thought things are janky, it still works as my daily driver).

Generally speaking, it'd probably be best to automate .deb, appimage, flatpak, and Windows builds (maybe mac if someone can be bothered to help us and has the mac development stack, not automated I guess).

Higher Priority:

We'll need to fix the way Versioning works so we can actual cut releases, this is probably some changes to heckimp.
We need to fix the about dialog shenanigans by figuring out why heckimp breaks the xsltproc and/or patching it out of the about dialog so the heckimp user has more control over it.

Lower priority:

Maybe some patch-shipping support for heckimp. Granted upstream's 3.0 stuff is a very moving target but we could freeze our release branch at a specific version of it.
Maybe we can fix python and vala scripts

Even though we fork the upstream development version, we should think about how we can get PIKA into the hands of actual users (even thought things are janky, it still works as my daily driver). Generally speaking, it'd probably be best to automate .deb, appimage, flatpak, and Windows builds (maybe mac if someone can be bothered to help us and has the mac development stack, not automated I guess). Higher Priority: - We'll need to fix the way Versioning works so we can actual cut releases, this is probably some changes to heckimp. - We need to fix the about dialog shenanigans by figuring out why heckimp breaks the xsltproc and/or patching it out of the about dialog so the heckimp user has more control over it. Lower priority: - Maybe some patch-shipping support for heckimp. Granted upstream's 3.0 stuff is a very moving target but we could freeze our release branch at a specific version of it. - Maybe we can fix python and vala scripts

cassowary commented

2023-12-07 22:07:13 +01:00

I have written a shell script that lets us build inside of a docker image for debian-based builds. This could probably be mutated into a .deb packager (with deps), but for now produces tarballs of /usr/local and expects the user to install the deps after untarring it. It's pretty easy to discover the deps we can probably automate it by deploying it into a clean docker, and then picking out the 'not found' on ldd outputs.