Bruno Haible <br...@clisp.org> writes:
> 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). We could also probably cache based on (g)libc version, kernel version, compiler & linker version, and any dependencies which gnulib modules may use (e.g. OpenSSL). While that might sound a bit much, it should be pretty quick to calculate compared to no cache at all. With that, you can do pretty well, I think. Whether or not it's worth it is another question. We'd still need people to be responsible about it (not use it recklessly, just when they're developing and know when their system changes). I wasn't aware of the Python tool work and am intrigued.
