bump version to 5.17.1

1 files changed, 16 insertions, 16 deletions

diff --git a/INSTALL b/INSTALL
index 333e80940c..1445cd9a6d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -534,7 +534,7 @@ The directories set up by Configure fall into three broad categories.
 
 =item Directories for the perl distribution
 
-By default, Configure will use the following directories for 5.17.0.
+By default, Configure will use the following directories for 5.17.1.
 $version is the full perl version number, including subversion, e.g.
 5.12.3, and $archname is a string like sun4-sunos,
 determined by Configure.  The full definitions of all Configure
@@ -845,7 +845,7 @@ must contain a space separated list of directories under the site_perl
 directory, and has to include architecture-dependent directories separately,
 eg.
 
-       sh Configure -Dinc_version_list="5.17.0/x86_64-linux 5.14.0" ...
+       sh Configure -Dinc_version_list="5.16.0/x86_64-linux 5.16.0" ...
 
 When using the newer perl, you can add these paths again in the
 PERL5LIB environment variable or with perl's -I runtime option.
@@ -2387,9 +2387,9 @@ won't interfere with another version.  (The defaults guarantee this for
 libraries after 5.6.0, but not for executables. TODO?)  One convenient
 way to do this is by using a separate prefix for each version, such as
 
-	sh Configure -Dprefix=/opt/perl5.17.0
+	sh Configure -Dprefix=/opt/perl5.17.1
 
-and adding /opt/perl5.17.0/bin to the shell PATH variable.  Such users
+and adding /opt/perl5.17.1/bin to the shell PATH variable.  Such users
 may also wish to add a symbolic link /usr/local/bin/perl so that
 scripts can still start with #!/usr/local/bin/perl.
 
@@ -2402,13 +2402,13 @@ seriously consider using a separate directory, since development
 subversions may not have all the compatibility wrinkles ironed out
 yet.
 
-=head2 Upgrading from 5.16.0 or earlier
+=head2 Upgrading from 5.17.0 or earlier
 
-B<Perl 5.17.0 may not be is binary incompatible with Perl 5.16.0 or
-earlier Perl release.>  Perl modules having binary parts
+B<Perl 5.17.1 may not be binary compatible with Perl 5.17.0 or
+earlier Perl releases.>  Perl modules having binary parts
 (meaning that a C compiler is used) will have to be recompiled to be
-used with 5.17.0.  If you find you do need to rebuild an extension with
-5.17.0, you may safely do so without disturbing the older
+used with 5.17.1.  If you find you do need to rebuild an extension with
+5.17.1, you may safely do so without disturbing the older
 installations.  (See L<"Coexistence with earlier versions of perl 5">
 above.)
 
@@ -2441,15 +2441,15 @@ Firstly, the bare minimum to run this script
      print("$f\n");
   }
 
-in Linux with perl-5.17.0 is as follows (under $Config{prefix}):
+in Linux with perl-5.17.1 is as follows (under $Config{prefix}):
 
   ./bin/perl
-  ./lib/perl5/5.17.0/strict.pm
-  ./lib/perl5/5.17.0/warnings.pm
-  ./lib/perl5/5.17.0/i686-linux/File/Glob.pm
-  ./lib/perl5/5.17.0/feature.pm
-  ./lib/perl5/5.17.0/XSLoader.pm
-  ./lib/perl5/5.17.0/i686-linux/auto/File/Glob/Glob.so
+  ./lib/perl5/5.17.1/strict.pm
+  ./lib/perl5/5.17.1/warnings.pm
+  ./lib/perl5/5.17.1/i686-linux/File/Glob.pm
+  ./lib/perl5/5.17.1/feature.pm
+  ./lib/perl5/5.17.1/XSLoader.pm
+  ./lib/perl5/5.17.1/i686-linux/auto/File/Glob/Glob.so
 
 Secondly, for perl-5.10.1, the Debian perl-base package contains 591 files,
 (of which 510 are for lib/unicore) totaling about 3.5MB in its i386 version.