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


Bruno Haible <bruno@clisp.org> writes:

> Sam James wrote:
>> > 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).
>
> We are talking about different things.
> 1) First comes the './autogen.sh' execution (or 'bootstrap'), which
>    generates files, by calling gnulib-tool and the Autotools.
> 2) Then comes the './configure' step.
>
> We are talking about caching the result of 1).
> You seem to be thinking about 2).

Oh, I see. Thanks!

>
> Bruno



  reply	other threads:[~2024-02-19 23:18 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
2024-02-19 23:11             ` Bruno Haible
2024-02-19 23:17               ` Sam James [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87ttm4kpra.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=simon@josefsson.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).