Ah, thank you for clarifying and the great suggestion. I'll pull in the latest bootstrap from gnulib and send it out for review hopefully this evening for the Grub maintainer's consideration.
Thank you! Andrew On Sat, Aug 23, 2025 at 5:34 PM Collin Funk <collin.fu...@gmail.com> wrote: > Andrew Hamilton <adham...@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
