updated readmes for 8.0.5 releasecore_8_1_merge_2_10_99core_8_0_5_base

3 files changed, 19 insertions, 63 deletions

diff --git a/README b/README
index 8e5fa21..56ef91c 100644
--- a/README
+++ b/README
@@ -1,13 +1,13 @@
 The Tk Toolkit
 
-RCS: @(#) $Id: README,v 1.10 1999/01/04 19:25:26 rjohnson Exp $
+RCS: @(#) $Id: README,v 1.11 1999/02/09 03:46:27 stanton Exp $
 
 1. Introduction
 ---------------
 
 This directory and its descendants contain the sources and documentation
 for Tk, an X11 toolkit implemented with the Tcl scripting language.  The
-information here corresponds to Tk 8.0.5, which is the third patch update
+information here corresponds to Tk 8.0.5, which is the fifth patch update
 for Tk 8.0.  This release is designed to work with Tcl 8.0.5 and may not
 work with any other version of Tcl.
 
@@ -88,36 +88,6 @@ Before trying to compile Tk you should do the following things:
 	if it has been updated with patches.  Patch releases fix bugs
 	without changing any features, so you should normally use the
 	latest patch release for the version of Tk that you want. 
-	Patch releases are available in two forms.  A file like
-	tk8.0p1.tar.Z is a complete release for patch level 1 of Tk
-	version 8.0.  If there is a file with a higher patch level than
-	this release, just fetch the file with the highest patch level
-	and use it.
-
-	Patches are also available in the form of patch files that just
-	contain the changes from one patch level to another.  These
-	files have names like tk8.0p1.patch, tk8.0p2.patch, etc.  They
-	may also have .gz or .Z extensions to indicate compression.  To
-	use one of these files, you apply it to an existing release with
-	the "patch" program.  Patches must be applied in order:
-	tk8.0p1.patch must be applied to an unpatched Tk 8.0 release
-	to produce a Tk 8.0p1 release;  tk8.0p2.patch can then be
-	applied to Tk 8.0p1 to produce Tk 8.0p2, and so on. To apply an
-	uncompressed patch file such as tk8.0p1.patch, invoke a shell
-	command like the following from the directory containing this
-	file (you may need to replace "patch -p" with "patch -p0"
-	depending on your version of the patch program):
-	    patch -p < tk8.0p1.patch
-	If the patch file has a .gz extension, it was compressed with
-	gzip.  To apply it, invoke a command like the following:
-	    gunzip -c tk8.0p1.patch.gz | patch -p
-	If the patch file has a .Z extension, it was compressed with
-	compress.  To apply it, invoke a command like the following:
-	    zcat tk8.0p1.patch.Z | patch -p
-	If you're applying a patch to a release that has already been
-	compiled, then before applying the patch you should cd to the
-	"unix" subdirectory and type "make distclean" to restore the
-	directory to a pristine state.
 
 Once you've done this, change to the "unix" subdirectory if you're
 compiling under UNIX, "win" if you're compiling under Windows, or
diff --git a/unix/README b/unix/README
index 21a8890..80c6fc3 100644
--- a/unix/README
+++ b/unix/README
@@ -10,7 +10,7 @@ SGI, as well as PCs running Linux, BSDI, and SCO UNIX.  To compile for
 a PC running Windows, see the README file in the directory ../win.  To
 compile for a Macintosh, see the README file in the directory ../mac.
 
-RCS: @(#) $Id: README,v 1.2 1998/09/14 18:23:54 stanton Exp $
+RCS: @(#) $Id: README,v 1.3 1999/02/09 03:46:27 stanton Exp $
 
 How To Compile And Install Tk:
 ------------------------------
@@ -82,19 +82,11 @@ How To Compile And Install Tk:
     versions, either specify the version number or create a symbolic
     link (e.g. from "wish" to "wish8.0").
 
-If you have trouble compiling Tk, read through the file "porting.notes".
-It contains information that people have provided about changes they had
-to make to compile Tcl in various environments.  Or, check out the
-following Web URL:
-    http://www.sunlabs.com/cgi-bin/tcl/info.8.0
-This is an on-line database of porting information.  We make no guarantees
-that this information is accurate, complete, or up-to-date, but you may
-find it useful.  If you get Tk running on a new configuration and had to
-make non-trivial changes to do it, we'd be happy to receive new information
-to add to "porting.notes".  You can also make a new entry into the
-on-line Web database.  We're also interested in hearing how to change the
-configuration setup so that Tcl compiles on additional platforms "out of
-the box".
+If you have trouble compiling Tk, read through the file
+"porting.notes".  It contains information that people have provided
+about changes they had to make to compile Tcl in various environments.
+We're also interested in hearing how to change the configuration setup
+so that Tcl compiles on additional platforms "out of the box".
 
 Test suite
 ----------
diff --git a/win/README b/win/README
index 260eae1..b2727ae 100644
--- a/win/README
+++ b/win/README
@@ -4,7 +4,7 @@ by Scott Stanton
 Scriptics Corporation
 scott.stanton@scriptics.com
 
-RCS: @(#) $Id: README,v 1.7 1999/01/04 19:25:28 rjohnson Exp $
+RCS: @(#) $Id: README,v 1.8 1999/02/09 03:46:27 stanton Exp $
 
 1. Introduction
 ---------------
@@ -22,12 +22,12 @@ common source release.  The binary distribution is a self-extracting
 archive with a built-in installation script.
 
 Look for the binary release in the same location as the source release
-(ftp.scriptics.com:/pub/tcl/tcl8_0 or any of the mirror sites).  For most users,
-the binary release will be much easier to install and use.  You only
-need the source release if you plan to modify the core of Tcl, or if
-you need to compile with a different compiler.  With the addition of
-the dynamic loading interface, it is no longer necessary to have the
-source distribution in order to build and use extensions.
+(ftp.scriptics.com:/pub/tcl/tcl8_0 or any of the mirror sites).  For
+most users, the binary release will be much easier to install and use.
+You only need the source release if you plan to modify the core of
+Tcl, or if you need to compile with a different compiler.  With the
+addition of the dynamic loading interface, it is no longer necessary
+to have the source distribution in order to build and use extensions.
 
 3. Compiling Tk
 ----------------
@@ -62,21 +62,16 @@ find them.  Tk looks in one of two places for the library files:
 	2) In the lib\tk8.0 directory under the Tcl installation directory
 	   as specified in the registry:
 
-		For Windows NT & 95:
-		    HKEY_LOCAL_MACHINE\SOFTWARE\Scriptics\Tcl\8.0
-			Value Name is "Root"
-
-		For Win32s:
-		    HKEY_CLASSES_ROOT\SOFTWARE\Scriptics\Tcl\8.0\
+		HKEY_LOCAL_MACHINE\SOFTWARE\Scriptics\Tcl\8.0
+		Value Name is "Root"
 
 	2) Relative to the directory containing the current .exe.
 	    Tk will look for a directory "..\lib\tk8.0" relative to the
 	    directory containing the currently running .exe.
 
 Note that in order to run wish80.exe, you must ensure that tcl80.dll,
-tclpip80.dll (plus tcl1680.dll under Win32s), and tk80.dll are on your
-path, in the system directory, or in the directory containing
-wish80.exe.
+tclpip80.dll, and tk80.dll are on your path, in the system directory,
+or in the directory containing wish80.exe.
 
 4. Test suite
 -------------
@@ -100,7 +95,6 @@ Windows beta version of Tk:
 - Some "wm" functions don't map to Windows and aren't implemented;
   others should map, but just aren't implemented.  The worst offenders
   are the icon manipulation routines.
-- Under Win32s, you can only start one instance of Wish at a time.
 - Color management on some displays doesn't work properly resulting in
   Tk switching to monochrome mode.
 - Tk seems to fail to draw anything on some Matrox Millenium cards.