Simon Josefsson wrote:
> I now
> remember that something like this was discussed before:
>
> https://git.savannah.gnu.org/cgit/libidn.git/commit/?id=9ae53e866a6fafa56db26d184ccae9c39dae7446
> https://lists.gnu.org/archive/html/bug-gnulib/2021-05/msg00077.html
I see... you are building a cache that will become invalid when either
- the bootstrap.conf changes, or
- there is a change in gnulib in one of the request modules (in the
module description or in code).
> My usage pattern is to frequently re-bootstrap from a clean git checkout
> to confirm that my changes still work properly for fresh rebuilds. The
> reason is that I don't trust 'make clean', 'make distclean', etc.
With your cache, you'll now have to trust your decision whether to use
or erase the cache. But at least, you can automate this decision:
erase the cache when bootstrap.conf or the referenced gnulib submodule
was changed.
In other words, replace the cache file name
/home/jas/.local/gnulib-bootstrap-cache/bootstrap-files-for-libidn.tar.gz
with
/home/jas/.local/gnulib-bootstrap-cache/bootstrap-files-for-libidn-<gnulib_submodule_commit>-<hash_code_of_bootstrap.conf>.tar.gz
Bruno
