diff options
author | Jesse Vincent <jesse@bestpractical.com> | 2010-04-12 23:15:56 -0400 |
---|---|---|
committer | Jesse Vincent <jesse@bestpractical.com> | 2010-04-12 23:15:56 -0400 |
commit | cb47d8a5d4a3850a5c2237056982489145a27981 (patch) | |
tree | 38a86ba347e361e122324468e8c32a87c63dbacb /INSTALL | |
parent | 20d572319ce8b690b7b68fec6b58f8ac07b1d362 (diff) | |
download | perl-cb47d8a5d4a3850a5c2237056982489145a27981.tar.gz |
Bump to 5.13.0
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -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.12.0. +By default, Configure will use the following directories for 5.13.0. $version is the full perl version number, including subversion, e.g. -5.12.0 or 5.9.5, and $archname is a string like sun4-sunos, +5.13.0 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. @@ -2340,9 +2340,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.12.0 + sh Configure -Dprefix=/opt/perl5.13.0 -and adding /opt/perl5.12.0/bin to the shell PATH variable. Such users +and adding /opt/perl5.13.0/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. @@ -2357,11 +2357,11 @@ yet. =head2 Upgrading from 5.11.0 or earlier -B<Perl 5.12.0 is binary incompatible with Perl 5.11.1 and any earlier +B<Perl 5.13.0 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.12.0. If you find you do need to rebuild an extension with -5.12.0, you may safely do so without disturbing the older +used with 5.13.0. If you find you do need to rebuild an extension with +5.13.0, you may safely do so without disturbing the older installations. (See L<"Coexistence with earlier versions of perl 5"> above.) |