summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2011-01-20 14:36:28 -0500
committerJesse Vincent <jesse@bestpractical.com>2011-01-20 14:36:28 -0500
commit298a2886e2e4369d1549a8de440169a90ca1909a (patch)
treee321d96f699cc97f13901c791b21d475e672711a /INSTALL
parent65b2cfd1356d212fc0e84d242dfb47db113d673d (diff)
downloadperl-298a2886e2e4369d1549a8de440169a90ca1909a.tar.gz
Bump the perl version in various places to 5.13.9
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL14
1 files changed, 7 insertions, 7 deletions
diff --git a/INSTALL b/INSTALL
index cac05ec8e3..d448f9f366 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.8.
+By default, Configure will use the following directories for 5.13.9.
$version is the full perl version number, including subversion, e.g.
-5.13.8 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.9 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.
@@ -2374,9 +2374,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.8
+ sh Configure -Dprefix=/opt/perl5.13.9
-and adding /opt/perl5.13.8/bin to the shell PATH variable. Such users
+and adding /opt/perl5.13.9/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.
@@ -2391,11 +2391,11 @@ yet.
=head2 Upgrading from 5.13.7 or earlier
-B<Perl 5.13.8 is binary incompatible with Perl 5.13.7 and any earlier
+B<Perl 5.13.9 is binary incompatible with Perl 5.13.7 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.8. If you find you do need to rebuild an extension with
-5.13.8, you may safely do so without disturbing the older
+used with 5.13.9. If you find you do need to rebuild an extension with
+5.13.9, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)