On 5/13/24 7:45 PM, Paul Eggert wrote: > I messed up. However, the shell implementation of gnulib-tool diagnoses my > mistake right away, before going on its slow way: > > $ GNULIB_TOOL_IMPL=sh ./gnulib-tool --create-testdir --dir foo -h stdbit > mkdir: cannot create directory ‘foo’: File exists > Module list with included dependencies (indented): > absolute-header > alignasof
One benefit to gnulib-tool.sh being slow is you have more time to read the messages. :) > Perhaps both implementations should quickly exit in this situation, come to > think of it. I've run into this a few times where the test-driver script fails to be patched. I never bothered fixing it because the shell script does it too. I feel like gnulib-tool should just fail if the destination directory exists. Is that what you wanted too or am I misunderstanding? Collin
