Emphasize the drawbacks of the --symlink option.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 0e296318703e948aace8bb7f3834b685f5ef59ef..3bee978f4093c66b38c0920d79c0550b4b9e8e73 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2006-10-08  Bruno Haible  <bruno@clisp.org>
+
+       * gnulib-tool.texi: Emphasize the drawbacks of the --symlink option.
+
 2006-09-19  Karl Berry  <karl@gnu.org>
 
        * gnulib.texi: note about the license texinfo files.

diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index f8e3f83d50f81d519c4fa82ca08590c6b0ea993a..01ea29d1208e25c96c931c328ff9aef56b18b9e5 100644 (file)
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -90,8 +90,14 @@ are copied into the directory specified by @samp{AC_CONFIG_AUX_DIR} in
 neither is specified, the current directory is assumed.
 
 @code{gnulib-tool} can make symbolic links instead of copying the
-source files.  Use the @samp{--symbolic} (or @samp{-s} for short) option
-to do this.
+source files.  The option to specify for this is @samp{--symlink}, or
+@samp{-s} for short.  This can be useful to save a few kilobytes of disk
+space.  But it is likely to introduce bugs when @code{gnulib} is updated;
+it is more reliable to use @samp{gnulib-tool --update} (see below)
+to update to newer versions of @code{gnulib}.  Furthermore it requires
+extra effort to create self-contained tarballs, and it may disturb some
+mechanism the maintainer applies to the sources.  For these reasons,
+this option is generally discouraged.
 
 @code{gnulib-tool} will overwrite any pre-existing files, in
 particular @file{Makefile.am}.  Unfortunately, separating the