You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
squash! Do not create cygwin symlinks. Instead use deep copy of files/folders.
The original patch to change the symbolic link behavior to create deep
copies instead did so in a bit of a hacky way: it used the
`WSYM_sysfile` code path, not introducing a separate mode. This makes it
impossible for users to ask for Cygwin's behavior (and it also poses a
maintenance burden: for example, we had to specifically disable Cygwin's
code to prefer to create WSL-style symlinks whenever possible instead of
using the original Cygwin hack to use special-formed system files).
Proposed new commit message when rebasing the MSYS2 patches on top of
the next Cygwin runtime version:
Instead of creating Cygwin symlinks, use deep copy by default
The new `winsymlinks` mode `deepcopy` (which is made the default) lets
calls to `symlink()` create (deep) copies of the source file/directory.
This is necessary because unlike Cygwin, MSYS2 does not try to be its
own little ecosystem that lives its life separate from regular Win32
programs: the latter have _no idea_ about Cygwin-emulated symbolic links
(i.e. system files whose contents start with `!<symlink>\xff\xfe` and
the remainder consists of the NUL-terminated, UTF-16LE-encoded symlink
target).
To support Cygwin-style symlinks, the new mode `sysfile` is introduced.
Co-authored-by: Johannes Schindelin <[email protected]>
0 commit comments