Hi James,
do you have any objections to calling the 'gnulib-tool --import' step with
--symlink?
Recently I got trapped for a change in gnulib, and didn't notice that the files
in 'gl/' (imported by the bootstrap scipt) are copies from gnulib; I didn't see
a gnulib change there. I expected those files to be symlinks.
Using --symlink would also save some disk space and work faster.
WDYT?
Thanks & have a nice day,
Berny
>From c1dd7c8a94480f6088c2397cad3e1d9b49dde37b Mon Sep 17 00:00:00 2001
From: Bernhard Voelker <m...@bernhard-voelker.de>
Date: Sun, 19 Apr 2020 15:25:45 +0200
Subject: [PATCH] maint: bootstrap gnulib with --symlink
* bootstrap.conf (gnulib_tool_option_extras): Add --symlink option.
---
bootstrap.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bootstrap.conf b/bootstrap.conf
index e6452956..2ad23be8 100644
--- a/bootstrap.conf
+++ b/bootstrap.conf
@@ -222,7 +222,7 @@ bootstrap_post_import_hook() {
# For compatibility with 'import-gnulib.sh', add gnulib's test directory.
# 'gnulib-tests/Makefile' is mentioned in 'configure.ac'
-gnulib_tool_option_extras="--tests-base=gnulib-tests --with-tests"
+gnulib_tool_option_extras="--tests-base=gnulib-tests --with-tests --symlink"
# Additional xgettext options to use. Use "\\\newline" to break lines.
--
2.26.1
