summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2009-10-20 10:49:51 -0400
committerJesse Vincent <jesse@bestpractical.com>2009-10-20 10:49:51 -0400
commit6f15df4765b853018c7db3e5cae157305d7c5e12 (patch)
tree32e544a9d7e3b8c5624f888c9d46667879bec45f /INSTALL
parent795c888f79c01883bb0f6b8275aa4bcec88eb29d (diff)
downloadperl-6f15df4765b853018c7db3e5cae157305d7c5e12.tar.gz
Bump 5.11.0 -> 5.11.1 in all sorts of places it's (oh so unfortunately) hardcoded
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL16
1 files changed, 8 insertions, 8 deletions
diff --git a/INSTALL b/INSTALL
index 24013313e6..b9d1c3efac 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.0.
+By default, Configure will use the following directories for 5.11.1.
$version is the full perl version number, including subversion, e.g.
-5.11.0 or 5.9.5, and $archname is a string like sun4-sunos,
+5.11.1 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.
@@ -2351,9 +2351,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.0
+ sh Configure -Dprefix=/opt/perl5.11.1
-and adding /opt/perl5.11.0/bin to the shell PATH variable. Such users
+and adding /opt/perl5.11.1/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.
@@ -2366,13 +2366,13 @@ seriously consider using a separate directory, since development
subversions may not have all the compatibility wrinkles ironed out
yet.
-=head2 Upgrading from 5.10.x or earlier
+=head2 Upgrading from 5.11.0 or earlier
-B<Perl 5.11.0 is binary incompatible with Perl 5.10.x and any earlier
+B<Perl 5.11.1 is binary incompatible with Perl 5.11.0 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.0. If you find you do need to rebuild an extension with
-5.11.0, you may safely do so without disturbing the older
+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
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)