X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=Porting%2Fpumpkin.pod;h=54725ce946348eb817cbd88e7bc648c87440da6e;hb=94655993b20cb9c52b7d861dd02a2575bace49b1;hp=efb9d2675a20784f68f112f05d5163890b142c3a;hpb=24f415b42b16ca2ea955d5f4fc7cc29cb1fc7054;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/Porting/pumpkin.pod b/Porting/pumpkin.pod
index efb9d26..54725ce 100644
--- a/Porting/pumpkin.pod
+++ b/Porting/pumpkin.pod
@@ -43,7 +43,7 @@ to perl5-porters-request@perl.org .
 
 Archives of the list are held at:
 
-    http://www.rosat.mpe-garching.mpg.de/mailing-lists/perl-porters/
+    http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/
 
 =head1 How are Perl Releases Numbered?
 
@@ -590,7 +590,7 @@ to change the version number near the top of the F<Changes> file.
 
 =head2 Todo
 
-The F<Todo> file contains a roughly-catgorized unordered list of
+The F<pod/perltodo.pod> file contains a roughly-catgorized unordered list of
 aspects of Perl that could use enhancement, features that could be
 added, areas that could be cleaned up, and so on.  During your term as
 pumpkin-holder, you will probably address some of these issues, and
@@ -602,7 +602,7 @@ You might like, early in your pumpkin-holding career, to see if you
 can find champions for partiticular issues on the to-do list: an issue
 owned is an issue more likely to be resolved.
 
-There are also some more porting-specific L<Todo> items later in this
+There are also some more porting-specific L</Todo> items later in this
 file.
 
 =head2 OS/2-specific updates
@@ -1261,11 +1261,11 @@ a mail message from Larry:
 Given that it's already there, you can use it to override distribution modules.
 One way to do that is to add
 
-	ccflags="$ccflags -DAPPLLIB_EXP='"/my/override"'
+	ccflags="$ccflags -DAPPLLIB_EXP=\"/my/override\""
 	
 to your config.over file.  (You have to be particularly careful to get the
-double quotes in.  It might actually be easier to just #define it
-yourself in perl.c.)
+double quotes in.  APPLLIB_EXP must be a valid C string.  It might
+actually be easier to just #define it yourself in perl.c.)
 
 Then perl.c will put /my/override ahead of ARCHLIB and PRIVLIB.  Perl will
 also search architecture-specific and version-specific subdirectories of
@@ -1325,9 +1325,11 @@ Anyway, all this leads to quite obscure failures that are sure to drive
 casual users crazy.  Even experienced users will get confused :-).  Upon
 reflection, I'd say leave libperl.so in $archlib.
 
-=item 4.
+=back
+
+=head2 Indentation style
 
-Indentation style: over the years Perl has become a mishmash of
+Over the years Perl has become a mishmash of
 various indentation styles, but the original "Larry style" can
 probably be restored with (GNU) indent somewhat like this:
 
@@ -1340,8 +1342,6 @@ of consecutive assignments, which would truly wreck the layout in
 places like sv.c:Perl_sv_upgrade() or sv.c:Perl_clone_using().
 Similarly nicely aligned &&s, ||s and ==s would not be respected.
 
-=back
-
 =head1 Upload Your Work to CPAN
 
 You can upload your work to CPAN if you have a CPAN id.  Check out