Hi Dmitry, > The development is going to happen inside a standalone branch. > Once stuff becomes mature enough, it'll be pushed into the master.
I would like to make it easy for users to invoke gnulib-tool.py for users, without changing their autogen.sh / bootstrap / Makefile.devel /... scripts or recipes. I'll do this by introducing an environment variable, say, GNULIB_TOOL_PYTHON so that people can do $ GNULIB_TOOL_PYTHON=yes ./autogen.sh instead of $ ./autogen.sh This will be a couple of lines of code in gnulib-tool, to invoke gnulib-tool.py with the same arguments. The prerequisite for this is only that gnulib-tool.py is properly invokable through python or python3, and that it sits in the 'master' branch. It is *not* a requirement that it is "mature enough". Bruno
