diff options
Diffstat (limited to 'upstream/debian-unstable/man1/perl5242delta.1')
| -rw-r--r-- | upstream/debian-unstable/man1/perl5242delta.1 | 158 |
1 files changed, 158 insertions, 0 deletions
diff --git a/upstream/debian-unstable/man1/perl5242delta.1 b/upstream/debian-unstable/man1/perl5242delta.1 new file mode 100644 index 00000000..671d5674 --- /dev/null +++ b/upstream/debian-unstable/man1/perl5242delta.1 @@ -0,0 +1,158 @@ +.\" -*- mode: troff; coding: utf-8 -*- +.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) +.\" +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. +.ie n \{\ +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds C` +. ds C' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is >0, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX +.. +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{\ +. if \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. if !\nF==2 \{\ +. nr % 0 +. nr F 2 +. \} +. \} +.\} +.rr rF +.\" ======================================================================== +.\" +.IX Title "PERL5242DELTA 1" +.TH PERL5242DELTA 1 2024-01-12 "perl v5.38.2" "Perl Programmers Reference Guide" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH NAME +perl5242delta \- what is new for perl v5.24.2 +.SH DESCRIPTION +.IX Header "DESCRIPTION" +This document describes differences between the 5.24.1 release and the 5.24.2 +release. +.PP +If you are upgrading from an earlier release such as 5.24.0, first read +perl5241delta, which describes differences between 5.24.0 and 5.24.1. +.SH Security +.IX Header "Security" +.ie n .SS "Improved handling of '.' in @INC in base.pm" +.el .SS "Improved handling of '.' in \f(CW@INC\fP in base.pm" +.IX Subsection "Improved handling of '.' in @INC in base.pm" +The handling of (the removal of) \f(CW\*(Aq.\*(Aq\fR in \f(CW@INC\fR in base has been +improved. This resolves some problematic behaviour in the approach taken in +Perl 5.24.1, which is probably best described in the following two threads on +the Perl 5 Porters mailing list: +<http://www.nntp.perl.org/group/perl.perl5.porters/2016/08/msg238991.html>, +<http://www.nntp.perl.org/group/perl.perl5.porters/2016/10/msg240297.html>. +.SS """Escaped"" colons and relative paths in PATH" +.IX Subsection """Escaped"" colons and relative paths in PATH" +On Unix systems, Perl treats any relative paths in the PATH environment +variable as tainted when starting a new process. Previously, it was allowing a +backslash to escape a colon (unlike the OS), consequently allowing relative +paths to be considered safe if the PATH was set to something like \f(CW\*(C`/\e:.\*(C'\fR. The +check has been fixed to treat \f(CW\*(C`.\*(C'\fR as tainted in that example. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "Updated Modules and Pragmata" +.IX Subsection "Updated Modules and Pragmata" +.IP \(bu 4 +base has been upgraded from version 2.23 to 2.23_01. +.IP \(bu 4 +Module::CoreList has been upgraded from version 5.20170114_24 to 5.20170715_24. +.SH "Selected Bug Fixes" +.IX Header "Selected Bug Fixes" +.IP \(bu 4 +Fixed a crash with \f(CW\*(C`s///l\*(C'\fR where it thought it was dealing with UTF\-8 when it +wasn't. +[GH #15543] <https://github.com/Perl/perl5/issues/15543> +.SH Acknowledgements +.IX Header "Acknowledgements" +Perl 5.24.2 represents approximately 6 months of development since Perl 5.24.1 +and contains approximately 2,500 lines of changes across 53 files from 18 +authors. +.PP +Excluding auto-generated files, documentation and release tools, there were +approximately 960 lines of changes to 17 .pm, .t, .c and .h files. +.PP +Perl continues to flourish into its third decade thanks to a vibrant community +of users and developers. The following people are known to have contributed +the improvements that became Perl 5.24.2: +.PP +Aaron Crane, Abigail, Aristotle Pagaltzis, Chris 'BinGOs' Williams, Dan +Collins, David Mitchell, Eric Herman, Father Chrysostomos, James E Keenan, Karl +Williamson, Lukas Mai, Renee Baecker, Ricardo Signes, Sawyer X, Stevan Little, +Steve Hay, Tony Cook, Yves Orton. +.PP +The list above is almost certainly incomplete as it is automatically generated +from version control history. In particular, it does not include the names of +the (very much appreciated) contributors who reported issues to the Perl bug +tracker. +.PP +Many of the changes included in this version originated in the CPAN modules +included in Perl's core. We're grateful to the entire CPAN community for +helping Perl to flourish. +.PP +For a more complete list of all of Perl's historical contributors, please see +the \fIAUTHORS\fR file in the Perl source distribution. +.SH "Reporting Bugs" +.IX Header "Reporting Bugs" +If you find what you think is a bug, you might check the articles recently +posted to the comp.lang.perl.misc newsgroup and the perl bug database at +<https://rt.perl.org/> . There may also be information at +<http://www.perl.org/> , the Perl Home Page. +.PP +If you believe you have an unreported bug, please run the perlbug program +included with your release. Be sure to trim your bug down to a tiny but +sufficient test case. Your bug report, along with the output of \f(CW\*(C`perl \-V\*(C'\fR, +will be sent off to perlbug@perl.org to be analysed by the Perl porting team. +.PP +If the bug you are reporting has security implications which make it +inappropriate to send to a publicly archived mailing list, then see +"SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec +for details of how to report the issue. +.SH "SEE ALSO" +.IX Header "SEE ALSO" +The \fIChanges\fR file for an explanation of how to view exhaustive details on +what changed. +.PP +The \fIINSTALL\fR file for how to build Perl. +.PP +The \fIREADME\fR file for general stuff. +.PP +The \fIArtistic\fR and \fICopying\fR files for copyright information. |