In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/54356a6f6c5b66c92d16521d060160496e44de3c?hp=6f15df4765b853018c7db3e5cae157305d7c5e12>
- Log ----------------------------------------------------------------- commit 54356a6f6c5b66c92d16521d060160496e44de3c Author: Jesse Vincent <[email protected]> Date: Tue Oct 20 10:54:38 2009 -0400 release manager guide notes updated M Porting/release_managers_guide.pod commit 172dd9593c69d24c1273d593b8e9ca4fadf1f99c Author: Jesse Vincent <[email protected]> Date: Tue Oct 20 10:52:07 2009 -0400 suidperl is no longer available. INSTALL should not say it is M INSTALL ----------------------------------------------------------------------- Summary of changes: INSTALL | 22 +++------------------- Porting/release_managers_guide.pod | 15 ++++++++++++++- 2 files changed, 17 insertions(+), 20 deletions(-) diff --git a/INSTALL b/INSTALL index b9d1c3e..9582876 100644 --- a/INSTALL +++ b/INSTALL @@ -1315,25 +1315,9 @@ process or the Perl build process will not help you with these. =head2 suidperl -suidperl is an optional component, which is normally neither built -nor installed by default. From perlfaq1: - - On some systems, setuid and setgid scripts (scripts written - in the C shell, Bourne shell, or Perl, for example, with the - set user or group ID permissions enabled) are insecure due to - a race condition in the kernel. For those systems, Perl versions - 5 and 4 attempt to work around this vulnerability with an optional - component, a special program named suidperl, also known as sperl. - This program attempts to emulate the set-user-ID and set-group-ID - features of the kernel. - -Because of the buggy history of suidperl, and the difficulty -of properly security auditing as large and complex piece of -software as Perl, we cannot recommend using suidperl and the feature -should be considered deprecated. - -Instead, use a tool specifically designed to handle changes in -privileges, such as B<sudo>. +suidperl was an optional component of earlier releases of perl. It is no +longer available. Instead, use a tool specifically designed to handle +changes in privileges, such as B<sudo>. =head1 make depend diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index daa4fcc..8c1c51e 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -241,6 +241,8 @@ Once all version numbers have been bumped, re-run the checks. Then run again without the -x option, to check that dual-life modules are also sensible. + $ ./perl -Ilib Porting/cmpVERSION.pl -d ~/my_perl-tarballs/perl-5.10.0 . + =item * I<You MAY SKIP this step for SNAPSHOT> @@ -285,7 +287,7 @@ careful not change text like "this was fixed in 5.10.0"! Then run: $ Porting/bump-perl-version -u < /tmp/scan -which will update all the files shown; then commit the changes. +which will update all the files shown. Be particularly careful with F<INSTALL>, which contains a mixture of C<5.10.0>-type strings, some of which need bumping on every release, and @@ -295,6 +297,17 @@ this line in README.vms needs special handling: rename perl-5^.10^.1.dir perl-5_10_1.dir +Have a look a couple lines up from that. You'll see roman numerals. +Update those too. Find someone with VMS clue if you have to update +the Roman numerals for a .0 release. + +Commit your changes: + + $ git st + $ git diff + B<review the delta carefully> + + $ git commit -a -m 'Bump the perl version in various places for 5.x.y' =item * -- Perl5 Master Repository
