Since this module is by far the most complex (compared to 'relocatable-lib'
and 'relocatable-script'), and since users may have packages that install
libraries or scripts, but no programs, there is no point in a naming
convention that suggests that 'relocatable' is the most basic among the
three modules. I am therefore renaming it:
2007-03-03 Bruno Haible <[EMAIL PROTECTED]>
* modules/relocatable-prog: Renamed from modules/relocatable.
* doc/relocatable-maint.texi: Talk about module 'relocatable-prog'.
--- doc/relocatable-maint.texi 2 Mar 2007 01:53:11 -0000 1.2
+++ doc/relocatable-maint.texi 3 Mar 2007 20:35:19 -0000
@@ -20,17 +20,17 @@
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.
-The @code{relocatable} module aims to ease the process of making a GNU
-program relocatable. It helps overcome two obstacles. First, it aids
+The @code{relocatable-prog} module aims to ease the process of making a
+GNU program relocatable. It helps overcome two obstacles. First, it aids
with relocating the hard-coded references to absolute file names that
GNU programs often contain. These references must be fixed up at
runtime if a program is to be successfully relocated. The
[EMAIL PROTECTED] module provides a function @code{relocate} that
[EMAIL PROTECTED] module provides a function @code{relocate} that
does this job.
Second, the loader must be able to find shared libraries linked to
relocatable executables or referenced by other shared libraries linked
-to relocatable executables. The @code{relocatable} module helps out
+to relocatable executables. The @code{relocatable-prog} module helps out
here in a platform-specific way:
@itemize
@@ -58,7 +58,7 @@
@enumerate
@item
-Import the @code{relocatable} module.
+Import the @code{relocatable-prog} module.
@item
In every program, add to @code{main} as the first statement (even
