> Why is the mingw container not Arch Linux based such that pacman doesnt need > to be compiled? I would also expect that other packages take less time to > install.
Personal preference and the fact that most other CI resources are also Debian/Ubuntu based. I don't know if it would make a difference in package installation speed. Why and does it matter if it is a few seconds faster or slower? Furthermore, I'm not sure if ArchLinux's pre-compiled pacman can be used as is. The self-compiled variant uses a different path layout. > Do I understand correctly that the Docker image is updated manually, and a PR > on geany or G-P would download that pre-build image (or even use cached > copies) instead of rolling the container every single time (including > compiling pacman)? First, the current image available in the registry is built and uploaded by me manually. As said in the G-P PR this is an open TODO. A CI job will try to pull the image from the registry, due to current permissions settings this probably works only for jobs trigger from the repository itself (master builds and PRs created from the repository itself, not forks). CI jobs which are triggered by a forked repository will *not* have access to the image in the registry and so fall back to build it on the fly. In theory, we could push that on the fly built image into the registry. But I consider this too risky to open doors for malicious input. I didn't make my mind up finally on how to deal with the proper image management: - Should we build it reguarly independent from the CI jobs? - Which repository handles updating the image, Geany or Geany-PLugins or Infrastructure? - Should we open the restrictions and allow access to the image also for forked repositories? > Remark #1: Generally speaking I'm not a huge fan of docker but since that > doesn't run on my machine it's probably OK :-) It took me a few years also to see its advantages and why it might be useful. I think in this it's a quite convenient tool to have a isolated environment to build the code. Remark #2: I use arch linux on my machine. If you don't feel familiar enough with it I can maybe help you. I used Arch Linux until a few months ago as well, but IMO this is no reason to use it here :). Again, I guess it won't make a relevant different except that we would have to port the existing scripts. I guess more people out there are already or can get familiar with a Debian/Ubuntu system. Do you have any other reason for switching to ArchLinux? -- Reply to this email directly or view it on GitHub: https://github.com/geany/infrastructure/pull/7#issuecomment-1250374793 You are receiving this because you are subscribed to this thread. Message ID: <geany/infrastructure/pull/7/[email protected]>
