Re: symlinks to programs

On 7/4/24 20:17, Bruno Haible wrote: PPS. Why do we have both gnulib-tool.py and .gnulib-tool.py? Is this commented in the source code? Yes, there is a large comment about it in .gnulib-tool.py. OK, but that comment explains why .gnulib-tool.py is separate from the main body of the Python pro

Re: symlinks to programs

Hi Paul, Paul Eggert writes: > OK, but that comment explains why .gnulib-tool.py is separate from the > main body of the Python program. But why are there two shell scripts > gnulib-tool and gnulib-tool.py? Can't the latter be folded into the > former? That would be simpler and faster. I can ha

Re: symlinks to programs

Paul Eggert wrote: > But why are there two shell scripts > gnulib-tool and gnulib-tool.py? Can't the latter be folded into the > former? That would be simpler and faster. This will be done when we drop support for the old shell-based implementation and for the GNULIB_TOOL_IMPL environment variab

Re: symlinks to programs

Collin Funk wrote: > The addition of .gnulib-tool.py means that $PYTHONPATH is no longer > needed. Yes, I removed the use of PYTHONPATH in . Bruno

Re: gnulib-tool.py: Fix crash when no ACLOCAL_AMFLAGS is found.

On 6/2/24 14:51, Collin Funk wrote: I don't know enough about Autotools to tell if anything silly can be done using this trick. Not that you would run auto* in a project that you don't trust anyways... Right, but the glitch is worth documenting. I installed the attached into Autoconf.From 3a7a

Re: gnulib-tool.py: Fix crash when no ACLOCAL_AMFLAGS is found.

Paul Eggert writes: > Right, but the glitch is worth documenting. I installed the attached > into Autoconf. Thanks! Collin