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.
After adjusting the `PKGBUILD` to reflect that this package is supposed
to track Cygwin v3.5.x, this commit adjusts the patches accordingly (the
trick was performed by `./update-patches.sh`, of course).
This corresponds to https://github.com/msys2/msys2-runtime/pull/204.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
After copying the files verbatim from `msys2-runtime`, this change
reflects that we want to build the MSYS2 runtime v3.5.x in this package.
Note: To make things easier to review, the patches are not yet adjusted
by running `./update-patches.sh`. That will be left for the next commit.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
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>
