"Gary V. Vaughan" <g...@gnu.org> writes: >> I haven't tried yet but a quick look into the code seems to confirm >> that Gary's `bootstrap' file can do that. In case this is true I >> really recommend to use his version as the default in gnulib. > > I agree with this too :) > > However, I understand that reviewing a few thousand lines of new shell > code (even though heavily inspired by the bootstrap and bootstrap.conf > scripts of several prominent GNU projects) is no easy task.
One solution might be to add your script under another name, and let the two scripts continue to exist and be used independently. I'm interested to try both approaches eventually, although so far the current gnulib bootstrap script has appeared to me as too restricted to allow me to move away from what I'm using today (put all gnulib files in each project's own git repo). For example, for some reason, my projects often follow a pattern where they need to have multiple gnulib instances. Last time I looked, bootstrap couldn't handle this, can yours? /Simon
