make it more obvious when target (sub)directory is skipped
This should avoid the sort of confusion seen in: https://github.com/aspiers/shell-env/issues/1
This commit is contained in:
parent
497a067621
commit
07a84541f1
5 changed files with 65 additions and 5 deletions
|
@ -550,12 +550,12 @@ sub should_skip_target_which_is_stow_dir {
|
|||
|
||||
# Don't try to remove anything under a stow directory
|
||||
if ($target eq $self->{stow_path}) {
|
||||
debug(2, "Skipping target which was current stow directory $target");
|
||||
warn "WARNING: skipping target which was current stow directory $target\n";
|
||||
return 1;
|
||||
}
|
||||
|
||||
if ($self->marked_stow_dir($target)) {
|
||||
debug(2, "Skipping protected directory $target");
|
||||
warn "WARNING: skipping protected directory $target\n";
|
||||
return 1;
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue