summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorTatsuhiko Miyagawa <miyagawa@bulknews.net>2010-10-20 15:55:11 -0700
committerTatsuhiko Miyagawa <miyagawa@bulknews.net>2010-10-20 15:56:07 -0700
commit7dffbb6a6e777ec59d29f6802b76bf34e68e8146 (patch)
treec460e7d306ae62630587011a906b3511ec6b0cbe /INSTALL
parentb141c43c04aa77df154811acd708b7b951e3963d (diff)
downloadperl-7dffbb6a6e777ec59d29f6802b76bf34e68e8146.tar.gz
Bump version to 5.13.6
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index 67620bf304..06654acaf8 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.5.
+By default, Configure will use the following directories for 5.13.6.
$version is the full perl version number, including subversion, e.g.
-5.13.5 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.6 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.
@@ -2373,9 +2373,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.5
+ sh Configure -Dprefix=/opt/perl5.13.6
-and adding /opt/perl5.13.5/bin to the shell PATH variable. Such users
+and adding /opt/perl5.13.6/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.
@@ -2390,11 +2390,11 @@ yet.
=head2 Upgrading from 5.13.4 or earlier
-B<Perl 5.13.5 is binary incompatible with Perl 5.13.4 and any earlier
+B<Perl 5.13.6 is binary incompatible with Perl 5.13.5 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.5. If you find you do need to rebuild an extension with
-5.13.5, you may safely do so without disturbing the older
+used with 5.13.6. If you find you do need to rebuild an extension with
+5.13.6, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)