summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorZefram <zefram@fysh.org>2010-12-19 15:04:53 +0000
committerZefram <zefram@fysh.org>2010-12-19 15:04:53 +0000
commite03f126cfb07245dc7a7a3f70b2c7443689be3ed (patch)
treec421850ee67f8388c9d7d05ef930bbad1c16e0bc /INSTALL
parent170968377abf9e056b7362f557315dd607605f38 (diff)
downloadperl-e03f126cfb07245dc7a7a3f70b2c7443689be3ed.tar.gz
bump perl version number for 5.13.8
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index c4347ef2fc..f99a0a0cc6 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.7.
+By default, Configure will use the following directories for 5.13.8.
$version is the full perl version number, including subversion, e.g.
-5.13.7 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.8 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.7
+ sh Configure -Dprefix=/opt/perl5.13.8
-and adding /opt/perl5.13.7/bin to the shell PATH variable. Such users
+and adding /opt/perl5.13.8/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.7 is binary incompatible with Perl 5.13.5 and any earlier
+B<Perl 5.13.8 is binary incompatible with Perl 5.13.7 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.7. If you find you do need to rebuild an extension with
-5.13.7, you may safely do so without disturbing the older
+used with 5.13.8. If you find you do need to rebuild an extension with
+5.13.8, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)