summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorSteve Hay <steve.m.hay@googlemail.com>2010-02-20 16:28:04 +0000
committerSteve Hay <steve.m.hay@googlemail.com>2010-02-20 16:28:04 +0000
commit84e09a8c4c3ab0da4efb6250a91ff5d3425e35b7 (patch)
tree145fca50aec25bdbc3482829ea5f3442b20325a5 /INSTALL
parent33c1015fda04899ea576248c4c328da8ad24e12c (diff)
downloadperl-84e09a8c4c3ab0da4efb6250a91ff5d3425e35b7.tar.gz
Bump version to 5.11.5
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index 14af173e2a..2d90d85018 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.4.
+By default, Configure will use the following directories for 5.11.5.
$version is the full perl version number, including subversion, e.g.
-5.11.4 or 5.9.5, and $archname is a string like sun4-sunos,
+5.11.5 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.
@@ -2336,9 +2336,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.4
+ sh Configure -Dprefix=/opt/perl5.11.5
-and adding /opt/perl5.11.4/bin to the shell PATH variable. Such users
+and adding /opt/perl5.11.5/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.
@@ -2353,11 +2353,11 @@ yet.
=head2 Upgrading from 5.11.0 or earlier
-B<Perl 5.11.4 is binary incompatible with Perl 5.11.1 and any earlier
+B<Perl 5.11.5 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.4. If you find you do need to rebuild an extension with
-5.11.4, you may safely do so without disturbing the older
+used with 5.11.5. If you find you do need to rebuild an extension with
+5.11.5, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)