bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org,  Collin Funk <collin.funk1@gmail.com>
Subject: Re: gnulib-tool caching
Date: Mon, 19 Feb 2024 13:55:50 +0100	[thread overview]
Message-ID: <87plws4nqh.fsf@kaka.sjd.se> (raw)
In-Reply-To: <5243556.8YlivOVZr6@nimes> (Bruno Haible's message of "Mon, 19 Feb 2024 11:38:05 +0100")

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

Bruno Haible <bruno@clisp.org> writes:

> Simon Josefsson wrote:
>> is it possible to design a reliable
>> caching mechanism?  Something similar to CONFIG_SITE for autoconf?
> CONFIG_SITE is not reliable; that's the problem with it...
>> I find that ./gnulib-tool takes a long time and 95% of the time I use
>> it, it ended up doing exactly the same thing as it did last time I ran
>> it: copying a set of possibly patched files out of the gnulib directory.
> I use gnulib-tool with option --symlink in such cases. As long as the
> module descriptions don't change, you don't need to re-run gnulib-tool
> then.

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.  That
may not be a common work flow, but I'm pretty committed to it.  I now
remember that something like this was discussed before:


I don't recall if I actually had any real problems with that approach...
however I got a faster laptop and stoped using it to mimize any
deviation from standard gnulib workflows.

Maybe a hook below would allow further experiments?  I am not proposing
to commit this now since it is relatively easy for me to experiment with
improvements by adding this to the bootstrap.conf script on projects
that I work on.  The GNULIB_BOOTSTRAP_SITE also allows me to change my
setup without altering bootstrap.conf for every project I work on.


diff --git a/top/bootstrap-funclib.sh b/top/bootstrap-funclib.sh
index 9e40f4a3e4..9b8972f56c 100644
--- a/top/bootstrap-funclib.sh
+++ b/top/bootstrap-funclib.sh
@@ -194,6 +194,7 @@ bootstrap_sync=false
 # Make sure that bootstrap.conf is sourced from the current directory
 # if we were invoked as "sh bootstrap".
 conffile=`dirname "$me"`/bootstrap.conf
 test -r "$conffile" && . "$conffile"
 # ------------------------- Build-time prerequisites -------------------------

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

  reply	other threads:[~2024-02-19 12:55 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 [this message]
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
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=87plws4nqh.fsf@kaka.sjd.se \
    --to=bug-gnulib@gnu.org \
    --cc=bruno@clisp.org \
    --cc=collin.funk1@gmail.com \
    --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).