crypt add-on dokumentation patch

[Andreas Jaeger]

I've updated the FAQ and the install file to reflect that crypt is no
longer an addon.

Ok to commit?

Andreas

2000-07-05  Andreas Jaeger  <aj@suse.de>

	* manual/install.texi (Installation): Update information about
	add-ons.
	(Configuring and compiling): Update for glibc 2.2.

============================================================
Index: FAQ.in
--- FAQ.in	2000/04/21 03:37:35	1.102
+++ FAQ.in	2000/07/05 11:53:11
@@ -217,8 +217,8 @@
 ??addon	What are these `add-ons'?
 
 {UD} To avoid complications with export rules or external source code some
-optional parts of the libc are distributed as separate packages (e.g., the
-crypt package, see ?crypt).
+optional parts of the libc are distributed as separate packages, e.g., the
+linuxthreads package.
 
 To use these packages as part of GNU libc, just unpack the tarfiles in the
 libc source directory and tell the configuration script about them using the
@@ -227,7 +227,7 @@
 it doesn't, or if you want to select only a subset of the add-ons, give a
 comma-separated list of the add-ons to enable:
 
-	configure --enable-add-ons=crypt,linuxthreads
+	configure --enable-add-ons=linuxthreads
 
 for example.
 
@@ -237,9 +237,13 @@
 must be written to get everything running.
 
 Most add-ons are tightly coupled to a specific GNU libc version.  Please
-check that the add-ons work with the GNU libc.  For example the crypt and
-linuxthreads add-ons have the same numbering scheme as the libc and will in
-general only work with the corresponding libc.
+check that the add-ons work with the GNU libc.  For example the linuxthreads
+add-on has the same numbering scheme as the libc and will in general only
+work with the corresponding libc.
+
+{AJ} With glibc 2.2 the crypt add-on and with glibc 2.1 the localedata
+add-on have been integrated into the normal glibc distribution, crypt and
+localedata are therefore not anymore add-ons.
 
 ??	My XXX kernel emulates a floating-point coprocessor for me.
 	Should I enable --with-fp?
@@ -472,20 +476,8 @@
 	`crypt' and `setkey'.  Why aren't these functions in the
 	libc anymore?
 
-{UD} The US places restrictions on exporting cryptographic programs and
-source code.  Until this law gets abolished we cannot ship the cryptographic
-functions together with glibc.
-
-The functions are available, as an add-on (see ?addon).  People in the US
-may get it from the same place they got GNU libc from.  People outside the
-US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
-pub/linux/glibc, or another archive site outside the USA.  The README explains
-how to install the sources.
-
-If you already have the crypt code on your system the reason for the failure
-is probably that you did not link with -lcrypt.  The crypto functions are in
-a separate library to make it possible to export GNU libc binaries from the
-US.
+
+Removed.  Does not apply anymore.
 
 ??	When I use GNU libc on my Linux system by linking against
 	the libc.so which comes with glibc all I get is a core dump.
============================================================
Index: manual/install.texi
--- manual/install.texi	2000/04/21 03:42:25	1.41
+++ manual/install.texi	2000/07/05 11:53:13
@@ -15,9 +15,9 @@
 separate tarfiles which you unpack into the top level of the source
 tree.  Then you give @code{configure} the @samp{--enable-add-ons} option
 to activate them, and they will be compiled into the library.  As of the
-2.1 release, two important components of glibc are distributed as
-``official'' add-ons.  Unless you are doing an unusual installation, you
-should get them both.
+2.2 release, one important component of glibc is distributed as
+``official'' add-ons: the linuxthreads add-on.  Unless you are doing an
+unusual installation, you should get this.
 
 Support for POSIX threads is maintained by someone else, so it's in a
 separate package.  It is only available for Linux systems, but this will
@@ -43,7 +43,7 @@
 
 GNU libc can be compiled in the source directory, but we strongly advise to
 build it in a separate build directory.  For example, if you have unpacked
-the glibc sources in @file{/src/gnu/glibc-2.1.0}, create a directory
+the glibc sources in @file{/src/gnu/glibc-2.2.0}, create a directory
 @file{/src/gnu/glibc-build} to put the object files in.  This allows
 removing the whole build directory in case an error occurs, which is the
 safest way to get a fresh start and should always be done.
@@ -52,7 +52,7 @@
 at the top level of the source tree.  In the scenario above, you'd type
 
 @smallexample
-$ ../glibc-2.1.0/configure @var{args...}
+$ ../glibc-2.2.0/configure @var{args...}
 @end smallexample
 
 Please note that even if you're building in a separate build directory,

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de