-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
os: Windows Symlink support #5750
Labels
Milestone
Comments
Maybe. Symlinks aren't very common at least on Windows, and I imagine most Windows tools would be confused by them. I think returning an error on Windows is an acceptable implementation. But leaving open here for tracking. Labels changed: added priority-later, os-windows, removed priority-triage. Status changed to Accepted. |
Comment 3 by raul.san@sent.com: "Symlinks aren't very common at least on Windows, and I imagine most Windows tools would be confused by them." When you built a cross-system application, you expect that it works in every system; and since Windows enables symlinks I don't see a real issue to add its usage from Go. |
https://golang.org/cl/86160044/ doesn't reference this issue, but should. |
fwiw: https://gist.github.com/bradleypeabody/10572010 I personally feel that the Windows symlink functionality is lame and it is not surprising that nobody wants to mess with this feature (the fact that symlink creation requires administrator privileges by default is especially annoying). However, the above does seem work (bar possibly some edge cases I'm not aware of) and could be used as the basis for an implementation. |
Issue #7878 has been merged into this issue. |
Closed as duplicate issue #7878 is about hard links. I have a patch to fix this. May be hardlinks are not common in both windows and linux, but they are implemented for go/linux and it makes harder to port linux code to windows if there is inconsistent implementation. Attachments:
|
Note that patches in bug reports will be lost. Please see http://golang.org/doc/contribute.html. Thanks. |
CL https://golang.org/cl/86160044 mentions this issue. |
This issue was closed by revision cf521ce. Status changed to Fixed. |
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jun 25, 2018
Fixes golang#5750. https://code.google.com/p/go/issues/detail?id=5750 os: Separate windows from posix. Implement windows support. path/filepath: Use the same implementation as other platforms syscall: Add/rework new APIs for Windows LGTM=alex.brainman R=golang-codereviews, alex.brainman, gobot, rsc, minux CC=golang-codereviews https://golang.org/cl/86160044
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jul 9, 2018
Fixes golang#5750. https://code.google.com/p/go/issues/detail?id=5750 os: Separate windows from posix. Implement windows support. path/filepath: Use the same implementation as other platforms syscall: Add/rework new APIs for Windows LGTM=alex.brainman R=golang-codereviews, alex.brainman, gobot, rsc, minux CC=golang-codereviews https://golang.org/cl/86160044
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by raul.san@sent.com:
The text was updated successfully, but these errors were encountered: