summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorChris 'BinGOs' Williams <chris@bingosnet.co.uk>2010-11-20 14:37:14 +0000
committerChris 'BinGOs' Williams <chris@bingosnet.co.uk>2010-11-20 14:37:14 +0000
commit13796ecdc4344226ccb17819eaa5b15d26149a86 (patch)
tree44292328b47fc8230a58848025f485aedacc23e6 /INSTALL
parent9946686ee0b3ada8e0512262416bb5150e0e0108 (diff)
downloadperl-13796ecdc4344226ccb17819eaa5b15d26149a86.tar.gz
Bump the perl version in various places for v5.13.7
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index 4c4c43c149..c4347ef2fc 100644
--- a/INSTALL
+++ b/INSTALL
@@ -530,9 +530,9 @@ 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.13.6.
+By default, Configure will use the following directories for 5.13.7.
$version is the full perl version number, including subversion, e.g.
-5.13.6 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.7 or 5.9.5, and $archname is a string like sun4-sunos,
determined by Configure. The full definitions of all Configure
variables are in the file Porting/Glossary.
@@ -2374,9 +2374,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.13.6
+ sh Configure -Dprefix=/opt/perl5.13.7
-and adding /opt/perl5.13.6/bin to the shell PATH variable. Such users
+and adding /opt/perl5.13.7/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.
@@ -2391,11 +2391,11 @@ yet.
=head2 Upgrading from 5.13.4 or earlier
-B<Perl 5.13.6 is binary incompatible with Perl 5.13.5 and any earlier
+B<Perl 5.13.7 is binary incompatible with Perl 5.13.5 and any earlier
Perl release.> Perl modules having binary parts
(meaning that a C compiler is used) will have to be recompiled to be
-used with 5.13.6. If you find you do need to rebuild an extension with
-5.13.6, you may safely do so without disturbing the older
+used with 5.13.7. If you find you do need to rebuild an extension with
+5.13.7, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)