summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorLeon Brocard <acme@astray.com>2009-11-18 17:19:20 +0000
committerLeon Brocard <acme@astray.com>2009-11-18 17:19:20 +0000
commitf80e964fac6f1e3cb66e1c5f3b4459e9f651a3e1 (patch)
treeba9744d9c7fa2c21b4464bac1ba8734d467043b8 /INSTALL
parent7d5ce19f132a0e6f57b7322ef65d83ebd308521e (diff)
downloadperl-f80e964fac6f1e3cb66e1c5f3b4459e9f651a3e1.tar.gz
Bump 5.11.1 -> 5.11.2 in all sorts of places it's (oh so unfortunately) hardcoded
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index 3d95ff8a02..2381beed4d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -524,9 +524,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.11.1.
+By default, Configure will use the following directories for 5.11.2.
$version is the full perl version number, including subversion, e.g.
-5.11.1 or 5.9.5, and $archname is a string like sun4-sunos,
+5.11.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.
@@ -2335,9 +2335,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.11.1
+ sh Configure -Dprefix=/opt/perl5.11.2
-and adding /opt/perl5.11.1/bin to the shell PATH variable. Such users
+and adding /opt/perl5.11.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.
@@ -2352,11 +2352,11 @@ yet.
=head2 Upgrading from 5.11.0 or earlier
-B<Perl 5.11.1 is binary incompatible with Perl 5.11.0 and any earlier
+B<Perl 5.11.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.11.1. If you find you do need to rebuild an extension with
-5.11.1, you may safely do so without disturbing the older
+used with 5.11.2. If you find you do need to rebuild an extension with
+5.11.2, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)