Hi Dimitry (and all),
I don't like to be so negative, but ... I was not aware of any general
agreement on replacing the current gnulib world with a Python-based
world.
Note that gnulib-tool now will be the name for the gnulib-tool.py.
It seems to me that gnulib will become completely unusable for me after
things like this are done.
directory inside user's entire machine (e.g. to /usr/share/gnulib).
Also copy doc subdirectory to /usr/share/doc.
I know it was just an example, but using /usr is certainly wrong.
4. Copy gnulib-tool to /usr/local/bin directory.
This seems to be suggesting, merely in passing, a fundamental change in
the way gnulib is intended to be used.
Maybe you should fork gnulib into pygnulib and maintain it as you like
there, and people who like it can use it, and those of us who have a
whole development structure built up around how gnulib is now can keep
using it as it is?
Best,
k
