2 undocumented bugs in chkstow
Robotic-Brain <[email protected]> Wed, 25 Mar 2020 14:38:57 +0100
| Newsgroups | gmane.comp.gnu.stow.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hello, General System information ========================== stow (GNU Stow) version 2.3.1 perl 5, version 30, subversion 1 (v5.30.1) built for x86_64-linux-thread-multi Linux 5.5.11-arch1-1 #1 SMP PREEMPT Sun, 22 Mar 2020 16:33:15 +0000 x86_64 GNU/Linux target=~ stowdir=~/.stowcfg workingdir=~/.stowcfg Bug 1: Documentation for 'chkstow -t' does not match implementation / behavior unclear ====================================================================================== The documentation states in section 10 Target Maintenance that the default setting for 'chkstow -t' is the parent of the current stow directory. However the implementation does not seem to honor this rule unless the environment variable STOW_DIR is set. In order to be consistent with the 'stow' command the current working directory should be used as fallback instead of /usr/local Bug 2: 'chkstow -t ~ -l' seems to do nothing ============================================ After reading the source code i seem to be running into this FIXME on line 112 in chkstow # FIXME: what if the stow dir is not called 'stow'? My stow dir is called '.stowcfg' This should either be fixed or documented under known bugs Regards Robotic-Brain