[svn:mod_parrot] r471 - mod_parrot/trunk

[email protected] Wed, 22 Oct 2008 11:48:54 -0700 (PDT)
Newsgroups perl.cvs.mod_parrot
Message-ID <[email protected]>
Author: jhorwitz
Date: Wed Oct 22 11:48:53 2008
New Revision: 471

Modified:
   mod_parrot/trunk/README

Log:
update to reflect reality


Modified: mod_parrot/trunk/README
==============================================================================
--- mod_parrot/trunk/README	(original)
+++ mod_parrot/trunk/README	Wed Oct 22 11:48:53 2008
@@ -18,8 +18,8 @@
 
 REQUIREMENTS
 ------------
-* Apache 2.0.x or 2.2.x
-* Parrot 0.5.1 (Hatachi) or a recent source tree (all tests pass as of r24887)
+* Apache 2.0.x or 2.2.x (2.4 may work but is untested)
+* Parrot 0.8.0 or a recent source tree (all tests pass as of r32075)
 * Perl 5.8.0 or later for configuration
 * Apache::Test 1.26 or later (for tests)
 
@@ -52,11 +52,15 @@
    and set the PARROT_RUNTIME environment variable to that directory.
    mod_parrot will then be able to find this file automatically.
 
-3) Preload your Parrot handler with ParrotLoad.  It can be PIR or compiled PBC.
+3) Load the PIR HLL layer:
+
+   ParrotLoadImmediate ModParrot/HLL/pir.pbc
+
+4) Load your Parrot handler with ParrotLoad.  It can be PIR or compiled PBC.
 
    ParrotLoad /path/to/your/code
 
-4) Configure a location and set the handler to "parrot-code", the official
+5) Configure a location and set the handler to "parrot-code", the official
    mod_parrot handler string.  Use ParrotHandler to tell mod_parrot what to
    run for the content handler by passing it the namespace you used in your
    code:
@@ -77,9 +81,9 @@
 
    Or use one or more of the other Parrot*Handlers.
 
-5) Restart Apache.
+6) Restart Apache.
 
-6) Go to the URL you configured and try out your new handler.
+7) Go to the URL you configured and try out your new handler.
 
 DOCUMENTATION
 -------------