I just thought it's a better match because it comes with pacman, but also because it is generally up-to-date w.r.t. to toolchains and wine. So we could build the Windows binaries using the latest and greatest toolchain.
Debian/Ubuntu is usually several years behind and I worry a bit if that might cause trouble in the future if mingw packages require a newer toolchain (mingw is also rolling like Arch AFAIK). But it's your choice. I think the current restrictions are OK. Perhaps we could auto-update the image based on CI but I wouldn't trigger that from Geany repos but this repository (this is where the dockerfile is after all). Do we have anything to lose when giving forks access to the image, like losing some GH actions budget to it? Anyway we can discuss that later and leave it to official repos for now. -- Reply to this email directly or view it on GitHub: https://github.com/geany/infrastructure/pull/7#issuecomment-1250917617 You are receiving this because you are subscribed to this thread. Message ID: <geany/infrastructure/pull/7/c1250917...@github.com>