We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
../foo
Deep symlink copy will fail in this situation:
test ├── data │ ├── case00 │ │ └── README.md │ ├── case01 │ │ └── README.md │ ├── case02 │ │ └── README.md │ ├── case03 │ │ ├── README.md │ │ ├── case01 -> test/data/case01 │ │ └── relative_case01 -> ../case01
Though it's entirely acceptable to have a symlink working only at a certain current working dir, most of the time, we have symlinks:
../something
The text was updated successfully, but these errors were encountered:
fix: symlink deep copy with relative path
2e0f623
fix otiai10#97
39c8e6a
changing from os.Readlink to filepath.EvalSymlinks worked in my local.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Deep symlink copy will fail in this situation:
Though it's entirely acceptable to have a symlink working only at a certain current working dir, most of the time, we have symlinks:
../something
). 🐛 This case doesn't work properly.The text was updated successfully, but these errors were encountered: