From: Collin Funk <collin.funk1@gmail.com>
To: Andrew Hamilton <adhamilt@gmail.com>
Cc: grub-devel@gnu.org, daniel.kiper@oracle.com, ghetman@gmail.com
Subject: Re: [PATCH 1/1] bootstrap: Ensure shallow GNULIB clone Works on Newer GIT
Date: Sat, 23 Aug 2025 15:34:35 -0700 [thread overview]
Message-ID: <875xedk6pw.fsf@gmail.com> (raw)
In-Reply-To: <CA+04=DaFCpYNHn0RGLOSHhUTXa2AfBqAhNSJ=TkvctcSRwrZPw@mail.gmail.com>
Andrew Hamilton <adhamilt@gmail.com> writes:
> Thank you for the input, I considered updating the bootstrap script from
> GNULIB to latest but decided it may be considered a higher risk change for
> the upcoming 2.14 release. Maybe I should investigate this further.
>
> Do you happen to know if there is any dependency between the newer
> bootstrap script and the latest GNULIB version? If not, I can give it a
> shot to pull in the latest bootstrap script if Daniel thinks that is still
> within scope for 2.14.
I am not active in Grub development, so I will defer anything related to
the release process/safe changes to them.
But I am a Gnulib committer, so the questions regarding bootstrap are in
my wheelhouse (somewhat :P). The bootstrap script imports files based on
a gnulib submodule (see GNU Grep, Coreutils, etc.) or, in Grub's case,
GNULIB_REVISION in bootstrap.conf. It doesn't depend on anything else in
Gnulib. It simply clones Gnulib, checks-out the correct commit, then
runs autoreconf, libtoolize, autopoint, or whatever else the package
uses.
Generally GNU packages do not distribute the bootstrap script in
tarballs as they should contain all Gnulib source files and the
generated configure script. This allows someone to build the package
without having autoconf, automake, etc. installed.
That is the long way of explaining that updating bootstrap should not be
problematic. :)
Collin
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2025-08-23 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 21:22 [PATCH 0/1] bootstrap: Reduce GNULIB Size on Newer GIT Andrew Hamilton
2025-08-23 21:22 ` [PATCH 1/1] bootstrap: Ensure shallow GNULIB clone Works " Andrew Hamilton
2025-08-23 21:44 ` Collin Funk
2025-08-23 22:01 ` Andrew Hamilton
2025-08-23 22:34 ` Collin Funk [this message]
2025-08-23 22:37 ` Andrew Hamilton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xedk6pw.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=adhamilt@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=ghetman@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.