-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Add Configure question for taint support" #19679
Conversation
To evaluate this p.r. I built blead at fc995cf with my regular configuration options, then built @leonerd's branch the same way, then compared their respective
Looks good. Just for reference, here's a similar diff starting with
|
I think this missed perlsec.pod, that needs a documentation update to also be reverted. |
As @Leont noted, perlsec.pod needs the section on "Checking for taint suppot" removing, and the reference to that section earlier on. The second paragraph in section "Strictness and warnings" of perlmodstyle should be removed. In perlipc.pod remove this text:
replace it with: "Note that perl can be built without taint support. There are two different modes: in one, -T will silently do nothing. In the other mode -T results in a fatal error". In perllocale.pod, remove this:
In perlrun.pod, remove this:
and this:
|
This reverts commit 39f8eb4. This is because of a variety of issues discussed Perl#19657 and at the PSC meeting 064 2022-04-22 https://www.nntp.perl.org/group/perl.perl5.porters/2022/04/msg263670.html
@neilb I believe that's all the docs changes you listed. PTAL. Should I squash these before merge, or leave them as two commits? |
pod/perlipc.pod
Outdated
Note that perl can be built without taint support, | ||
in which case -T silently does nothing | ||
(see L<perlsec> for how to check if your perl support taint checking). | ||
Note that perl can be built without taint support. THere are two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"THere"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the preceding sentence be removed entirely?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hrm, that was in Neil's suggested text. I think it's still technically true, it's just you have go to the long way round with -Accflags=...
rather than using a configure question.
At this point, what remains before this is merged? IMHO, this is the only known blocker. |
This reverts commit 39f8eb4 which was added in PR #19541
This is because of a variety of issues discussed #19657 and at the PSC meeting 064 2022-04-22 https://www.nntp.perl.org/group/perl.perl5.porters/2022/04/msg263670.html