Fix copying vendored files when they are symbolic links #183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I just noticed I added an extra |
alikates
force-pushed
the
fix_file_symlinks
branch
from
2e3b060
to
ab837c8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm working on a project where one vendored dependency uses symlinks for managing different SystemVerilog module versions. This was making bender's vendor commands to try to overwrite the symlink with the actual dereferenced file.
I assume this is not intended and the previous handling of symlinks was only for the special case where a vendored package has a symlink to another external directory. That's why I added another condition where the target of the symlink is an actual directory.