This section of documentation discusses using gnulib-tool to build and
test Gnulib. I've applied this patch to document Python should be
installed.
Although it technically isn't required until the shell script version
is removed, I wouldn't want to recommend creating a testdir with all
modules using the shell version. :)
Collin
>From cddc1650b8bc3447f1a934befaf5b1dffd547c71 Mon Sep 17 00:00:00 2001
From: Collin Funk <collin.fu...@gmail.com>
Date: Mon, 28 Oct 2024 19:59:35 -0700
Subject: [PATCH] doc: Mention Python dependency.
* doc/build-automation.texi (Building gnulib): Document that Python is
needed for gnulib-tool.
---
ChangeLog | 6 ++++++
doc/build-automation.texi | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 2ca86ce7a7..36047f37c8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2024-10-28 Collin Funk <collin.fu...@gmail.com>
+
+ doc: Mention Python dependency.
+ * doc/build-automation.texi (Building gnulib): Document that Python is
+ needed for gnulib-tool.
+
2024-10-28 Bruno Haible <br...@clisp.org>
doc: Improve usability of generated PDF.
diff --git a/doc/build-automation.texi b/doc/build-automation.texi
index ae9d6b774d..54aa218996 100644
--- a/doc/build-automation.texi
+++ b/doc/build-automation.texi
@@ -10,8 +10,8 @@ @node Building gnulib
Install the proper development tools. To build and test all of
Gnulib, you will need development tools for the programming languages
-C, C++, Java, and Perl, along with standard POSIX utilities such as
-@command{awk}, @command{make} and @command{sh}. You will also need
+C, C++, Java, Perl, and Python along with standard POSIX utilities such
+as @command{awk}, @command{make} and @command{sh}. You will also need
development tools that include Autoconf, Automake, Bison, Gettext,
Git, GNU M4, Gperf, Libtool, and Texinfo. Some of these tools are
needed only by some modules. More details can be found in Gnulib's
--
2.47.0
