On 5/15/21 1:01 AM, Simon Josefsson via Gnulib discussion list wrote:
However, running ./bootstrap remains painfully slow.
Amen!!!
Then a second run of ./bootstrap in the directory would avoid the
gnulib-tool step, and only run autoreconf and friends. A new cfg.mk
variable to tell ./bootstrap to avoid checking out the gnulib repository
and run gnulib-tool by default would be needed.
Thoughts?
I think most of the functionality I want could be achieved today by
clever use of 'AUTORECONF=true AUTOPOINT=true LIBTOOLIZE=true
./bootstrap' and clever cfg.mk instrumenting with some hook together
with './bootstrap --no-git'. So I could probably test my approach with
only minimal changes to ./bootstrap now.
I'd add it as "./bootstrap --brief" and no-op the commands internally.
I still think the best solution is to put much of the gnulib stuff into
an installable gnulib-dev package that would be required by the
bootstrap script. I proposed that about 2 decades ago, but we're still
spending gobs of compute and wall clock resources recomputing the same
stuff. :(
