Updated README files to reflect directory changes and new installEpics.

MakeRelease

@@ -10,6 +10,9 @@
 #    [-b] - For fully built release
 #
 # $Log$
+# Revision 1.3  1995/10/03  15:42:26  jba
+# Added *COPYRIGHT* files to release tar file.
+#
 # Revision 1.2  1995/08/28  15:49:54  jba
 # Added startup directory to release tar file
 #
@@ -54,8 +57,8 @@
 
 EPICS=${1};
 
-if [ ! -d include -o ! -d src ]; then
-	echo "Cannot find src or include, are you at the top of EPICS base ?"
+if [ ! -d src ]; then
+	echo "Cannot find src directory, are you at the top of EPICS base ?"
 	exit 1
 fi
 
@@ -115,12 +118,18 @@ if [ -d startup ];
 				>> /tmp/make_release.out.$$;
 	fi
 
-find config base/include base/man base/tools -name CVS -prune -o \
+find config -name CVS -prune -o \
 		! -type d -print >> /tmp/make_release.out.$$;
 
 # binary / library / default.dctsdr / <rec>Record.h / etc.
 if [ $FULLY_BUILT = "YES" ];
 	then
+		find base/include -name CVS -prune -o ! -type d -print \
+				>> /tmp/make_release.out.$$;
+
+		find base/man -name CVS -prune -o ! -type d -print \
+				>> /tmp/make_release.out.$$;
+
 		find base/bin -name CVS -prune -o ! -type d -print \
 				>> /tmp/make_release.out.$$;
 

README

@@ -68,8 +68,8 @@ NOTES:
       base.  These tar files are then meant to be untarred at that level.
       This release will include the "epics/config" directory.
 
-   2. EPICS binaries are kept in the bin/ARCH and lib/ARCH directories. 
-      EPICS shellscripts are kept in the tools directory.
+   2. EPICS binaries and shellscripts are installed into the bin/ARCH and
+      lib/ARCH directories. 
 
    3. During a normal build (a "make" or "make install"), the "depends"
       dependency will NOT be invoked.  Only if "make depends" is run

README.Linux

@@ -8,18 +8,7 @@
 
 2) At this point, support for Linux only involves channel access
    clients.  Since Vxworks is not available for Linux, you must
-   use other platforms for developing server side code.  As for
-   building databases with dct and gdct, this requires that the 
-   $EPICS/base/tools/makesdr script works properly. Since makesdr
-   is slated to be removed from the EPICS distribution in a future
-   release, we didn't feel it was important to include this capability
-   now.  Consequently, when you run make you will receive the error
-
-   gnumake[4]: *** [bldDefaultSdr] Error 127
-
-   and
-
-   gnumake[3]: *** [comsubs.o] Error 1
+   use other platforms for developing server side code.
 
 3) You MUST start caRepeater by hand before running a client.  
 Prior to running a client, you must run:

README.hp700_alpha

@@ -10,5 +10,3 @@
 
  might be necessary.
 
-- epics/base/tools/bsdinstall was written to replace install for hp.
-

README.solaris

@@ -11,9 +11,8 @@ solaris directory /usr/ccs/bin is in your search path.
 2. It is not possible to compile EPICS under Solaris 2 using only the
 GNU gcc compiler -- you must have the Sun SPARCworks ANSI C compiler.
 
-3. EPICS under Solaris 2 no longer uses the UCB compatability
-libraries.  It does require the /usr/ucb/install program however.  In
-order to ensure that the /usr/ucblib files are not inherited, you
+3. EPICS under Solaris 2 no longer uses the UCB compatability libraries.
+In order to ensure that the /usr/ucblib files are not inherited, you
 should ensure that your LD_LIBRARY_PATH environment variable does not
 include /usr/ucblib when you build any of the host tools.