On Sat, 2022-07-30 at 22:01 +0200, Bruno Haible wrote:
> > which seems to imply that unless I add that flag or set
> > bootstrap_sync in my bootstrap.conf file (which I did not), the
> > sync won't happen.
>
> In your case, the sync already happened. So, either you must have had
> bootstrap_sync=true
> in your bootstrap.conf, or you passed the option --bootstrap-sync
> manually.
Neither of those were the case; this was what I was trying (in too many
words) to say.
The build-aux/bootstrap script contains these lines related to
bootstrap-sync:
# Set this to true in bootstrap.conf to enable --bootstrap-sync by
# default.
bootstrap_sync=false
then later:
--bootstrap-sync)
bootstrap_sync=true;;
--no-bootstrap-sync)
bootstrap_sync=false;;
then later:
if ! test -f "$medir"/bootstrap-funclib.sh; then
# We have only completed the first phase of an upgrade from a bootstrap
# version < 2022-07-24. Need to do the second phase now.
bootstrap_sync=true
fi
if $bootstrap_sync; then
prepare_GNULIB_SRCDIR
upgrade_bootstrap
# Since we have now upgraded if needed, no need to try it a second time
below.
bootstrap_sync=false
fi
As you can see, it doesn't matter in any way what I set in my
bootstrap.conf file or the command line: the if-statement says if
bootstrap-funclib.sh doesn't exist, then bootstrap_sync will be set to
true regardless of its previous value.
Since obviously I don't have that file (since I was using the old
bootstrap), bootstrap_sync is set to true and the bootstrap sync
happens regardless.
As best as I can tell, this is a bug. If it's not then I don't
understand the point of having the option at all.
