-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSYS2 installation with a junction in its path #567
Comments
The Cygwin Citing Corinna (hopefully not against her will):
|
I have my |
Are there any updates?
|
I don't evil anyone is going to fix this for you. If the people here care about it then fell free to try to investigate. Be prepared to learn more about Cygwin than you wanted to. Windows supports symbolic links now so there no need to use junction points. |
@mingwandroid Windows symbolic links do not invalidate the issue. With every installation of Windows I used, they don't work by default, because I am not able to create them without Administrator privileges. And as I have tried to point out months ago, with a symbolic link to (I lose the interest to investigate more in the meantime. I have worked around to just not use them for specific directories like |
@mingwandroid Windows native symbolic links that are only permitted to Administrator does not resolve this problem(watch my prev post, dir command shows |
You can use developer mode, I done think that requires admin (once set that is, but I could be wrong). |
@mingwandroid True, but:
I hope there can be some fixes, not just workarounds. |
I made a bug report and patch for qt some years ago to treat junctions as symlinks. The bug report gets discussed even now. The current latest statement from Qt is that junctions aren't enough like symlinks for Qt to do this. |
Lets assume I've installed MSYS2 to:
C:/Junction/msys64/
, where Junction/ points toD:/Stuff/
the execution of
pacman -S pacman
then fails withbecause it wasn't aware of the junction.
Yet if msys64/ itself is a junction, it would actually work as it seems to resolve the junction/symlink in that case. This is also true if you let
C:/Junction
point to the entire driveD:/
(so you go like C:/Junction/Stuff/msys64)Also, if you create a junction
D:/AnotherJunction/
which points toC:/Junction/msys64/
you can actually see what happens internally:You can see that it resolved the first junction which was the msys64 "root" (
D:/AnotherJunction/
) but didn't resolve the actual full path.I've opened this issue following a discussion in #524 as my issue wasn't really related to that one. (just a side note as it annoyed me in the past) So check that other issue for my initial "report" and my there described msys2 update issues.
The text was updated successfully, but these errors were encountered: