dsync/dcmp: support symlinks targets changes #618
+92
−14
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.
Update
dsync
anddcmp
to detect a symlinks targets changes. In this case, the symlinks are reported to be different bydcmp
and are updated bydsync
.Note this works for
dsync
both with or withoutc, --contents
.New function
mfu_compare_symlinks()
is introduced in library API to factorize the logic for all commands.Method
In order to reproduce the bug and validate the patch, I wrote this little script
symlink.sh
:Before
Script output:
The content in files tree:
You can see that
link2
still points tofile2
despite the seconddsync
run.After
Script output:
The content in files tree:
You can see that
link2
now points tofile1
after the seconddsync
run.Note
I would like to emphasize that this work is sponsored by @cea-hpc.
fix #412