diff options
| author | Steve Hay <steve.m.hay@googlemail.com> | 2010-09-19 15:21:29 +0100 |
|---|---|---|
| committer | Steve Hay <steve.m.hay@googlemail.com> | 2010-09-19 15:21:29 +0100 |
| commit | f6c54c41d6f0ed9ba259ce4a5e564c3d6d3d7cd6 (patch) | |
| tree | 3d65b5eae979dc06e9b568c0027bd81a5d6549ce /INSTALL | |
| parent | fc1418b79d5643b6e4c9da7a69fea4e7ab23d3c6 (diff) | |
| download | perl-f6c54c41d6f0ed9ba259ce4a5e564c3d6d3d7cd6.tar.gz | |
Bump version to 5.13.5
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.4. +By default, Configure will use the following directories for 5.13.5. $version is the full perl version number, including subversion, e.g. -5.13.4 or 5.9.5, and $archname is a string like sun4-sunos, +5.13.5 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. @@ -2366,9 +2366,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.4 + sh Configure -Dprefix=/opt/perl5.13.5 -and adding /opt/perl5.13.4/bin to the shell PATH variable. Such users +and adding /opt/perl5.13.5/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. @@ -2381,13 +2381,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.3 or earlier +=head2 Upgrading from 5.13.4 or earlier -B<Perl 5.13.4 is binary incompatible with Perl 5.13.3 and any earlier +B<Perl 5.13.5 is binary incompatible with Perl 5.13.4 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.4. If you find you do need to rebuild an extension with -5.13.4, you may safely do so without disturbing the older +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 installations. (See L<"Coexistence with earlier versions of perl 5"> above.) |