summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorMatt S Trout <mst@shadowcat.co.uk>2010-06-21 22:45:11 +0100
committerMatt S Trout <mst@shadowcat.co.uk>2010-06-21 22:45:11 +0100
commit20a372dd3af0f5514aa5ab9f401ecbfacf31773e (patch)
tree9b8deb19df5ef33a213d55490fa8cf6a1b7e0096 /INSTALL
parentb3b1f4cbdf866b01b788f5c540305604818ca3ea (diff)
downloadperl-20a372dd3af0f5514aa5ab9f401ecbfacf31773e.tar.gz
Bump the perl version in various places for 5.13.2
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index 8f09a7ed86..32e14c4a43 100644
--- a/INSTALL
+++ b/INSTALL
@@ -529,9 +529,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.1.
+By default, Configure will use the following directories for 5.13.2.
$version is the full perl version number, including subversion, e.g.
-5.13.1 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.2 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.
@@ -2365,9 +2365,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.1
+ sh Configure -Dprefix=/opt/perl5.13.2
-and adding /opt/perl5.13.1/bin to the shell PATH variable. Such users
+and adding /opt/perl5.13.2/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.
@@ -2382,11 +2382,11 @@ yet.
=head2 Upgrading from 5.11.0 or earlier
-B<Perl 5.13.1 is binary incompatible with Perl 5.11.1 and any earlier
+B<Perl 5.13.2 is binary incompatible with Perl 5.11.1 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.1. If you find you do need to rebuild an extension with
-5.13.1, you may safely do so without disturbing the older
+used with 5.13.2. If you find you do need to rebuild an extension with
+5.13.2, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)