X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Frelocatable.texi;h=fca0ea5b6ed7614c96272123b5946d1f1a489b79;hb=a425462f784164b73297d8992075fd9aebd65a94;hp=0eccc8a900ac9c364eb6cc35229449fc19db891a;hpb=5ee9e1aa114f21d4eab5671f9136c94fd6422481;p=gnulib.git

diff --git a/doc/relocatable.texi b/doc/relocatable.texi
index 0eccc8a90..fca0ea5b6 100644
--- a/doc/relocatable.texi
+++ b/doc/relocatable.texi
@@ -15,26 +15,45 @@ privileges to install a binary package, and prevents installing two
 different versions of the same binary package.
 
 A relocatable program can be moved or copied to a different location
-on the filesystem.  It is possible to make symlinks to the installed
+on the file system.  It is possible to make symlinks to the installed
 and moved programs, and invoke them through the symlink. It is
 possible to do the same thing with a hard link @emph{only} if the hard
 link file is in the same directory as the real program.
 
 To configure a program to be relocatable, add
-@option{--enable-relocatable} to the @program{configure} command line.
-For reliability, it is best to also give a @option{--prefix} option
-pointing to an otherwise unused (and never used again) directory,
-e.g.@: @option{--prefix=/tmp/inst$$}.  This is recommended because on
-some OSes the executables remember the location of shared libraries
+@option{--enable-relocatable} to the @command{configure} command line.
+
+On some OSes the executables remember the location of shared libraries
 and prefer them over any other search path.  Therefore, such an
 executable will look for its shared libraries first in the original
 installation directory and only then in the current installation
-directory.
+directory.  Thus, for reliability, it is best to also give a
+@option{--prefix} option pointing to a directory that does not exist
+now and which never will be created, e.g.@:
+@option{--prefix=/nonexistent}.  You may use
+@code{DESTDIR=@var{dest-dir}} on the @command{make} command line to
+avoid installing into that directory.
+
+We do not recommend using a prefix writable by unprivileged users
+(e.g.@: @file{/tmp/inst$$}) because such a directory can be recreated
+by an unprivileged user after the original directory has been removed.
+We also do not recommend prefixes that might be behind an automounter
+(e.g.@: @file{$HOME/inst$$}) because of the performance impact of
+directory searching.
+
+Here's a sample installation run that takes into account all these
+recommendations:
+
+@example
+./configure --enable-relocatable --prefix=/nonexistent
+make
+make install DESTDIR=/tmp/inst$$
+@end example
 
 Installation with @option{--enable-relocatable} will not work for
 setuid or setgid executables, because such executables search only
 system library paths for security reasons.  Also, installation with
-@option{--enable-relocatable} might not work not OpenBSD, when the
+@option{--enable-relocatable} might not work on OpenBSD, when the
 package contains shared libraries and libtool versions 1.5.xx are used.
 
 The runtime penalty and size penalty are negligible on GNU/Linux (just