00dani/stow
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

manual: clarify the pros and cons and history of --compat

Browse source
This commit is contained in:
Adam Spiers 2024-04-05 22:24:00 +01:00
parent 4cde7eb19f
commit 238346f134
1 changed files with 9 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/stow.texi
View file

@ -489,13 +489,15 @@ doing. Verbosity levels are from 0 to 5; 0 is the default. Using
@item -p @item -p
@itemx --compat @itemx --compat
Scan the whole target tree when unstowing. By default, only Scan the whole target tree when unstowing. By default, only directories
directories specified in the @dfn{installation image} are scanned specified in the @dfn{installation image} are scanned during an unstow
during an unstow operation. Scanning the whole tree can be operation. Previously Stow scanned the whole tree, which can be
prohibitive if your target tree is very large. This option restores prohibitive if your target tree is very large, but on the other hand has
the legacy behaviour; however, the @option{--badlinks} option to the the advantage of unstowing previously stowed links which are no longer
@command{chkstow} utility may be a better way of ensuring that your present in the installation image and therefore orphaned. This option
installation does not have any dangling symlinks (@pxref{Target restores the legacy behaviour; however, the @option{--badlinks} option
to the @command{chkstow} utility may be a better way of ensuring that
your installation does not have any dangling symlinks (@pxref{Target
Maintenance}). Maintenance}).
@item -V @item -V