This way the package, and its dependencies, are installed, so there
shouldn't be any missing DLL dependencies.
This is closer to what MINGW-packages does (with ntldd), but the scripts
could most likely stand to be synced to be closer.
The find expression was broken for a couple of reasons: it does not run in a subshell (so cannot use && like that), and it needs split arguments not one quoted argument. Avoid having to call echo by using -printf argument.
Fixes#4611
In case we have a git clone from Linux that is accessed via cygwin git
the files executable status will be derived from the file content (shebang)
and won't match the git repo, leading to a initially dirty tree.
This can be worked around by setting "core.filemode=false", but let's try
to match the cygwin permissions with the in-repo permissions so this isn't
needed.
Cygwin v3.5.0 has been released end of January 2024, and we were _about_
to be on the brink to switch to MSYS2 runtime based on the Cygwin
runtime v3.5.x.
However:
- That would leave Windows 7/8 compatibility behind.
- There have been a couple of hiccups in our testing, which led us to
skip v3.5.0 already.
- We determined that a safer way would be to let users opt into using
v3.5.x first, kicking the tires, so to say.
So let's establish a `msys2-runtime-3.5` package (much like
`msys2-runtime-3.3`) to be able to easily revert to a known state really
quickly, including the ability to run on Windows 7.
For now, this is merely a verbatim copy of the files in `msys2-runtime`,
and the next commits will modify them to reflect the version bump.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Provides and conflicts with msys2-runtime, so can be used to replace it if wanted.
Keep this as a separate package to test for regressions in cygwin
and to have (in theory) a runtime that supports 32bit in the repo.
There is no guarantee for how long we are going to keep this.
