Could you please clarify documentation: about setup-msys2 HOT 7 CLOSED

Partial updates are a not supported use case in MSYS2.

installs should work though, as long as we don't remove those old packages from the server.

from setup-msys2.

You can also use this action with release: false (yeah, not sure about that naming) to use the system environment, which would gain you caching of packages specified via install: ..., and you could easily switch between the image/fresh environments, handle updates etc.

Thanks for writing this up, as you said it's not very clear.

from setup-msys2.

Thanks for pointing me to release: false. It is mentioned only 2 paragraphs below the one I quoted here, and I now remember seeing it, but somehow it did not register that this would be how I could use your action.

from setup-msys2.

I'll keep this open a bit if you don't mind. So we don't forget to improve the docs.

from setup-msys2.

Sure!

from setup-msys2.

In fact, I was waiting for actions/runner-images#1648 to be deployed. It was merged a couple of days ago, so it should be done in about a week. There are still reasons to keep using this Action (see actions/runner-images#1572), but docs need to be updated.

from setup-msys2.

At least this is what I understood and concluded that the Setup MSYS2 action is not for me, because the default msys2 installation seems to work fine so far.

Partial updates are a not supported use case in MSYS2. Therefore, if you need to install any package which is not already installed in the default MSYS2 installation, you should first pacman -Syu. That's where the 10min overhead can kick in. It is independent from what packages you want to have installed, as it will first update several GBs of preinstalled toolchains.

Conversely, this action ensures that only the minimal packages you need are installed and updated. Plus, as @lazka said, caching is enabled by default if you use install:.

from setup-msys2.