From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: beta-tester call draft
Date: Sun, 21 Apr 2024 00:46:16 +0200 [thread overview]
Message-ID: <6446424.Y5tXFbCU9c@nimes> (raw)
In-Reply-To: <34ecc803-8d4c-4ebd-8121-49dd08229cdb@cs.ucla.edu>
Hi Paul,
Thanks for the feedback.
> If you are using git submodules, something like this:
> $ git -C gnulib pull origin master
> $ git commit -m 'build: update gnulib submodule to latest' gnulib
With the newest 'bootstrap', this would not be needed. But many packages
still use older or forked 'bootstrap' variants, for which the option
'--no-git' does not do what one would expect. I'm adding this paragraph:
If the package is using a git submodule named 'gnulib', it is
also advisable to do
$ git commit -m 'build: Update gnulib submodule to latest.' gnulib
(as a preparation for step 5, because the --no-git option does
not work as expected in all variants of 'bootstrap').
> > 5. Regenerate the fetched and generated files of your package.
> > Depending on the packge, this may be a command such as
> > $ ./bootstrap --no-git --gnulib-srcdir=$GNULIB_SRCDIR
> > or
> > $ export GNULIB_SRCDIR; ./autopull.sh; ./autogen.sh
> > or, if no such script is available:
> > $ $GNULIB_SRCDIR/gnulib-tool --update
>
> Here, perhaps you can add, "If you are using git submodules, just run a
> plain './bootstrap'."
This would be a bit dangerous, because 'bootstrap', by default, switches
back to the stored commit.
> > If there is a failure, due to differences between the 'sh' and 'py'
> > results, please report it to <bug-gnulib@gnu.org>.
>
> I tried this on my well-worn copy of GNU diffutils, and got the
> following diagnostics. These were all diagnostics about backup files, or
> files I manually deleted by moving them into a '.del' subdirectory (an
> old habit of mine), or symlink loops that I had created to test.
>
> Perhaps the advice should start with, "Start with a fresh checkout from
> Git."
We want to give people trust in using the Python implementation also
in worn working directories, not only in fresh checkouts. And I want to
hear about bugs in worn working directories.
Now that the bug with dangling symlinks is fixed, I feel confident
*not* to ask for a fresh checkout.
Bruno
next prev parent reply other threads:[~2024-04-20 22:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 0:22 beta-tester call draft Bruno Haible
2024-04-20 0:39 ` Bruno Haible
2024-04-20 0:56 ` Collin Funk
2024-04-20 1:49 ` Bruno Haible
2024-04-20 4:27 ` Paul Eggert
2024-04-20 22:31 ` gnulib-tool: In sh+py mode, don't fail because of dangling symlinks Bruno Haible
2024-04-20 22:46 ` Bruno Haible [this message]
2024-04-20 9:38 ` beta-tester call draft Simon Josefsson via Gnulib discussion list
2024-04-20 22:50 ` gnulib-tool.py speedup Bruno Haible
2024-04-20 23:01 ` Collin Funk
2024-04-20 23:50 ` Bruno Haible
2024-04-21 0:53 ` Collin Funk
2024-04-20 10:21 ` beta-tester call draft Pádraig Brady
2024-04-20 13:05 ` Bernhard Voelker
2024-04-20 22:54 ` Bruno Haible
2024-04-20 22:57 ` Paul Eggert
2024-04-20 23:14 ` Bruno Haible
2024-04-21 10:53 ` Bernhard Voelker
2024-04-21 14:50 ` future Python evolution Bruno Haible
2024-04-21 15:14 ` Paul Eggert
2024-04-21 22:38 ` Bruno Haible
2024-04-22 7:05 ` Paul Eggert
2024-04-21 15:26 ` Bernhard Voelker
2024-04-28 14:14 ` Bernhard Voelker
2024-04-21 15:15 ` beta-tester call draft Janneke Nieuwenhuizen
2024-04-21 16:07 ` full-source bootstrap and Python Bruno Haible
2024-04-22 7:29 ` Simon Josefsson via Gnulib discussion list
2024-04-22 10:07 ` Bruno Haible
2024-04-22 10:06 ` Janneke Nieuwenhuizen
2024-04-22 11:24 ` Simon Josefsson via Gnulib discussion list
2024-04-22 15:48 ` Bruno Haible
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=6446424.Y5tXFbCU9c@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).