Reuben Thomas wrote:
> because gnulib-tool is on PATH. That's all I want really, I want
> gnulib-tool to be on my PATH and I was asking what I have to do to
> make that work.
Ah, that was the real question behind the question!
Karl Berry wrote:
> ln -s /gnulib/checkout/gnulib-tool ~/bin # adapted as needed, of course
>
> That's it.
>
> I agree that we should put this bit of info into the top-level
> README and/or the manual or wherever.
Done as follows:
2009-04-01 Bruno Haible <br...@clisp.org>
* doc/gnulib-tool.texi (Invoking gnulib-tool): Document how gnulib-tool
can be put into PATH.
Reported by Reuben Thomas <r...@sc3d.org>. Suggested by Karl Berry.
--- doc/gnulib-tool.texi.orig 2009-04-02 02:16:52.000000000 +0200
+++ doc/gnulib-tool.texi 2009-04-02 02:14:58.000000000 +0200
@@ -1,7 +1,7 @@
@node Invoking gnulib-tool
@chapter Invoking gnulib-tool
-...@c Copyright (C) 2005-2008 Free Software Foundation, Inc.
+...@c Copyright (C) 2005-2009 Free Software Foundation, Inc.
@c Permission is granted to copy, distribute and/or modify this document
@c under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -21,6 +21,17 @@
simplifies the management of source files, @file{Makefile.am}s and
@file{configure.ac} in packages incorporating Gnulib modules.
+...@file{gnulib-tool} is not installed in a standard directory that is
+contained in the @code{PATH} variable. It needs to be run directly in
+the directory that contains the Gnulib source code. You can do this
+either by specifying the absolute filename of @file{gnulib-tool}, or
+you can also use a symbolic link from a place inside your @code{PATH}
+to the @file{gnulib-tool} file of your preferred and most up-to-date
+Gnulib checkout, like this:
+...@smallexample
+$ ln -s $HOME/gnu/src/gnulib.git/gnulib-tool $HOME/bin/gnulib-tool
+...@end smallexample
+
Run @samp{gnulib-tool --help} for information. To get familiar with
@command{gnulib-tool} without affecting your sources, you can also try
some commands with the option @samp{--dry-run}; then
