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
While NTFS supports hardlinks, exFAT does not. This prevents some packages to be installed in an msys2 installation that is on an exFAT-formatted drive.
Instead of having all those packages created without hardlinks, or expect some "dereferencing" feature to get implemented in libarchive, I wonder if it's possible / a good idea to have a wrapper for link() that allows users to choose whether to do deep copy for link() like we do for symlink().
The text was updated successfully, but these errors were encountered:
I am not sure about their stand in doing any deep copy. If I am not misinterpreting #16, isn't doing deep copy a msys2 thing since the beginning?
Although how hardlinking is handled isn't bound to how symlinking is, I doubt that they would care to implement it for the former if not for the latter.
This is also more or less related to how msys2 manage packages (I mean, the fact that it does it "from within" the installation). I assume cygwin is less affected.
While NTFS supports hardlinks, exFAT does not. This prevents some packages to be installed in an msys2 installation that is on an exFAT-formatted drive.
Instead of having all those packages created without hardlinks, or expect some "dereferencing" feature to get implemented in libarchive, I wonder if it's possible / a good idea to have a wrapper for
link()
that allows users to choose whether to do deep copy forlink()
like we do forsymlink()
.The text was updated successfully, but these errors were encountered: