Regenerate META.yml

[p5sagit/p5-mst-13.2.git] / README.vms

diff --git a/README.vms b/README.vms
index 2c6a6b2..4c1e06c 100644 (file)
--- a/README.vms
+++ b/README.vms
@@ -268,10 +268,6 @@ inappropriate changes to configure.com or config_h.SH can render perl
 unbuildable; odds are that there's nothing in there you'll need to
 change.
 
-The one exception is the various *DIR install locations. Changing those
-requires changes in genconfig.pl as well.  Be really careful if you need to
-change these, as they can cause some fairly subtle problems.
-
 =head2 Socket Support (optional) for Perl on VMS
 
 Perl includes a number of functions for IP sockets, which are available if
@@ -280,21 +276,36 @@ optional addition to VMS, there are several different IP stacks available.
 How well integrated they are into the system depends on the stack, your 
 version of VMS, and the version of your C compiler.
 
-The most portable solution uses the SOCKETSHR library. In combination with
-either UCX or NetLib, this supports all the major TCP stacks (Multinet,
-Pathways, TCPWare, UCX, and CMU) on all versions of VMS Perl runs on, with
-all the compilers on both VAX and Alpha. The socket interface is also
-consistent across versions of VMS and C compilers. It has a problem with
-UDP sockets when used with Multinet, though, so you should be aware of
-that.
-
-The other solution available is to use the socket routines built into DEC
+The default solution available is to use the socket routines built into DEC
 C. Which routines are available depend on the version of VMS you're
 running, and require proper UCX emulation by your TCP/IP vendor.
 Relatively current versions of Multinet, TCPWare, Pathway, and UCX all
 provide the required libraries--check your manuals or release notes to see
 if your version is new enough.
 
+The other solution uses the SOCKETSHR library. Before VAX/VMS 5.5-2 it was
+the most portable solution.  The SOCKETSHR library has not been maintained
+since VAX/VMS 5.5-2, and it is not known if will even compile with the ANSI
+C that Perl currently requires.  It remains an option for historical reasons,
+just in case someone might find it useful.
+
+In combination with either UCX or NetLib, this supported all the major TCP
+stacks (Multinet, Pathways, TCPWare, UCX, and CMU) on all versions of VMS
+Perl ran on up to VAX/VMS 6.2 and Alpha VMS 1.5 with all the compilers on
+both VAX and Alpha. The portion of the socket interface was also consistent
+across versions of VMS and C compilers.
+
+It has a problem with UDP sockets when used with Multinet, though, so you
+should be aware of that.
+
+As of VAX/VMS 5.5-2 and later, CMU is the only TCP/IP program that requires
+socketshr, and the sources have been lost to the most recent CMU bug fixes,
+so CMU is limited to OpenVMS/VAX 6.2 or earlier, which is the last release
+that binaries for the last released patches are known to exist.
+
+There is currently no official web site for downloading either CMU or
+SOCKETSHR; however, copies may be found in the DECUS archives.
+
 =head1 Building Perl
 
 The configuration script will print out, at the very end, the MMS or MMK