Reported by Alexei Sholomitskiy <asholomitskiy84@gmail.com> in
<https://lists.gnu.org/archive/html/bug-gnulib/2023-07/msg00071.html>
and by Collin Funk <collin.funk1@gmail.com> in
<https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00007.html>.
* doc/build-automation.texi (Building gnulib): Discourage the use of
--create-megatestdir with all modules.
+2024-03-03 Bruno Haible <bruno@clisp.org>
+
+ doc: Update regarding --create-megatestdir.
+ Reported by Alexei Sholomitskiy <asholomitskiy84@gmail.com> in
+ <https://lists.gnu.org/archive/html/bug-gnulib/2023-07/msg00071.html>
+ and by Collin Funk <collin.funk1@gmail.com> in
+ <https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00007.html>.
+ * doc/build-automation.texi (Building gnulib): Discourage the use of
+ --create-megatestdir with all modules.
+
2024-03-01 Bruno Haible <bruno@clisp.org>
gnulib-tool.py: Clarify minimum supported Python version.
git checkout, use
@example
-gnulib-tool --create-megatestdir --with-tests --dir=...
+gnulib-tool --create-testdir --with-tests --dir=...
@end example
-Note: The created directory uses ca. 512 MB on disk.
+Alternatively, pick a small set of modules and run
+
+@example
+gnulib-tool --create-megatestdir --with-tests --dir=... autobuild MODULES
+@end example
+
+@noindent
+(You can't do this will all of Gnulib at once: @code{gnulib-tool} would run
+for a week and produce a directory that takes more than 100 GB, maybe even 1 TB,
+of disk space.)
@item Transfer gnulib directory