summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2022-04-27 14:36:50 -0600
committerKarl Williamson <khw@cpan.org>2022-05-06 11:48:46 -0600
commit1c22bc64c8fb9dc6909357e83d8055c210bcefc9 (patch)
tree8c916ab75babddb64b2ac5ad5598076904e54b73 /pod/perlhack.pod
parentc5c541a8280c2967c3ff69fc75fc867109e1831b (diff)
downloadperl-1c22bc64c8fb9dc6909357e83d8055c210bcefc9.tar.gz
perlhack: Fix some pod markup, overlong verbatim
the F<> marker shouldn't need to be told whether or not to use "" to demarcate its argument. It should know what to do. Also fix some overlong verbatim lines
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod15
1 files changed, 8 insertions, 7 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index ef2a0e311b..3665ba2746 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -527,9 +527,9 @@ In most cases, patches to modules in F<cpan/> should be sent upstream
and should not be applied to the Perl core individually. If a patch to
a file in F<cpan/> absolutely cannot wait for the fix to be made
upstream, released to CPAN and copied to blead, you must add (or
-update) a C<CUSTOMIZED> entry in the F<"Porting/Maintainers.pl"> file
+update) a C<CUSTOMIZED> entry in the F<Porting/Maintainers.pl> file
to flag that a local modification has been made. See
-F<"Porting/Maintainers.pl"> for more details.
+F<Porting/Maintainers.pl> for more details.
In contrast, modules in the F<dist/> directory are maintained in the
core.
@@ -1101,11 +1101,12 @@ Another P5P contributor recommended installation and use of Devel::PatchPerl
for this situation, first to determine the version of perl at the commit in
question, then to patch the source code at that point to facilitate a build.
- $ perl -MDevel::PatchPerl -e \
- 'print Devel::PatchPerl->determine_version("/path/to/sourcecode"), "\n";'
- 5.11.1
- $ perl -MDevel::PatchPerl -e \
- 'Devel::PatchPerl->patch_source("5.11.1", "/path/to/sourcecode");'
+ $ perl -MDevel::PatchPerl -e \
+ 'print Devel::PatchPerl->determine_version("/path/to/sourcecode"),
+ "\n";'
+ 5.11.1
+ $ perl -MDevel::PatchPerl -e \
+ 'Devel::PatchPerl->patch_source("5.11.1", "/path/to/sourcecode");'
Once the source was patched, C<./Configure> and C<make test_prep> were called
and completed successfully, enabling confirmation of the findings in RT