Instead of calling msys2_shell.cmd call the respective launchers.
This unifies the way MSYS2 is started for most users and allows them
to set launch variables in the launcher .ini files.
While at it also rename the shortcuts to reference the environment names
instead of describing the environment. Not everyone might care or know
what these mean, so just unify them with the MSYSTEM env var which is
shown when starting bash right after.
Fixes#24
But don't fail, since most packages are missing the checksums still.
Once we have rebuilt everything in base we can treat errors there as fatal.
This shows us what is missing still..
While everything can asume base is there, packages in base also
implicitely depend on the runtime (and maybe filesystem?), so install
them first.
Until now we were just lucky that pacman installed them in the right order.
Fixes#40
Using a 7zip fork with zstandard support: https://github.com/mcmilk/7-Zip-zstd
Saves 20% CPU when extracting, also uses ~50MB less peak memory.
Downside is a 5% larger installer.
Install on both server 2016 and 2019, using the qt installer and the sfx inside docker
This makes the nightly builds safer to use, since they are likely never completely broken.
Fixes#27
- Maintenance tool is now installed as 'Uninstall_MSYS2.exe'
- 'Modify' button is disabled in Windows Settings 'Apps' list
- Add/Remove and Modify choices are hidden on Introduction page,
leaving 'Remove all components' as only available choice
- Even though it's no longer accessible, the Repository
configuration tab of the Settings dialog is also removed
Instead of maintaining a list ofr toplevel directories and files
that get added to the installer add everything.
Both the filesystem and the rebase package emit a warning on upgrade
because the list of path sto include wasn't updated. I don't see a reason why
we should exclude anything, so don't.
Fixes#10
