diff options
author | Florian Ragwitz <rafl@debian.org> | 2011-03-09 23:41:46 +0100 |
---|---|---|
committer | Florian Ragwitz <rafl@debian.org> | 2011-03-20 14:58:37 +0100 |
commit | c3c50a5a932e0a38b0e9dcbd324c27279e82557c (patch) | |
tree | 9adc848f237dc7b383b7f056442607d72ef901a6 /INSTALL | |
parent | f4d8fa6b1a34a0d395bede6b64af07f70dc1fc5a (diff) | |
download | perl-c3c50a5a932e0a38b0e9dcbd324c27279e82557c.tar.gz |
Bump the perl version for 5.13.11
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -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.10. +By default, Configure will use the following directories for 5.13.11. $version is the full perl version number, including subversion, e.g. -5.13.10 or 5.9.5, and $archname is a string like sun4-sunos, +5.13.11 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.10 + sh Configure -Dprefix=/opt/perl5.13.11 -and adding /opt/perl5.13.10/bin to the shell PATH variable. Such users +and adding /opt/perl5.13.11/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. @@ -2389,13 +2389,13 @@ seriously consider using a separate directory, since development subversions may not have all the compatibility wrinkles ironed out yet. -=head2 Upgrading from 5.13.9 or earlier +=head2 Upgrading from 5.13.10 or earlier -B<Perl 5.13.10 is binary incompatible with Perl 5.13.9 and any earlier +B<Perl 5.13.11 is binary incompatible with Perl 5.13.10 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.10. If you find you do need to rebuild an extension with -5.13.10, you may safely do so without disturbing the older +used with 5.13.11. If you find you do need to rebuild an extension with +5.13.11, you may safely do so without disturbing the older installations. (See L<"Coexistence with earlier versions of perl 5"> above.) |