bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Bruno Haible <bruno@clisp.org>
Cc: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: gnulib-tool caching
Date: Mon, 19 Feb 2024 22:24:23 +0000	[thread overview]
Message-ID: <871q98m6pn.fsf@gentoo.org> (raw)
In-Reply-To: <8818676.c0te8JeNC1@nimes>

Bruno Haible <bruno@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.

  reply	other threads:[~2024-02-19 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  1:24 [PATCH] gnulib-tool.py: Fix function call on incorrect object Collin Funk
2024-02-19  2:17 ` Bruno Haible
2024-02-19  8:59   ` Simon Josefsson via Gnulib discussion list
2024-02-19 10:38     ` gnulib-tool caching Bruno Haible
2024-02-19 12:55       ` Simon Josefsson via Gnulib discussion list
2024-02-19 21:50         ` Bruno Haible
2024-02-19 22:24           ` Sam James [this message]
2024-02-19 23:11             ` Bruno Haible
2024-02-19 23:17               ` Sam James
2024-02-19 18:37   ` [PATCH] gnulib-tool.py: Fix function call on incorrect object Collin Funk
2024-02-19 21:36     ` Bruno Haible
2024-02-19 22:42       ` Collin Funk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871q98m6pn.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=simon@josefsson.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).