a2beb7b371
Placing a .stow file in a directory tells Stow that this directory should be considered a Stow directory. This is already well-documented. There was an undocumented and slightly broken feature where placing a .nonstow file in a directory was treated in exactly the same way. The intention was for .nonstow to cause Stow to skip stowing into and unstowing from that directory and any of its descendants. However, it also caused Stow to consider symlinks into any of those directories as owned by Stow, even though that was clearly not the intention. So separate treatment of .stow and .nonstow markers, so that while both provide protection against Stow stowing and unstowing, only .stow affects the symlink ownership logic in find_stowed_path() and marked_stow_dir(). Probably no one uses the undocumented .nonstow feature, so it may make sense to remove this in future. |
||
---|---|---|
.. | ||
chkstow.t | ||
cleanup_invalid_links.t | ||
cli.t | ||
cli_options.t | ||
defer.t | ||
dotfiles.t | ||
examples.t | ||
find_stowed_path.t | ||
foldable.t | ||
ignore.t | ||
join_paths.t | ||
parent.t | ||
rc_options.t | ||
stow.t | ||
testutil.pm | ||
unstow.t | ||
unstow_orig.t |