perl.cvs.mod_parrot
[Top] [All Lists]

[svn:mod_parrot] r378 - mod_parrot/branches/configure/lib/ModParrot/Conf

Subject: [svn:mod_parrot] r378 - mod_parrot/branches/configure/lib/ModParrot/Configure
From: particle@xxxxxxxxxxxx
Date: Thu, 24 Jul 2008 12:05:57 -0700 (PDT)
Newsgroups: perl.cvs.mod_parrot

Author: particle
Date: Thu Jul 24 12:05:56 2008
New Revision: 378

Modified:
   mod_parrot/branches/configure/lib/ModParrot/Configure/Messages.pm

Log:
[config] make introduction and conclusion less verbose

Modified: mod_parrot/branches/configure/lib/ModParrot/Configure/Messages.pm
==============================================================================
--- mod_parrot/branches/configure/lib/ModParrot/Configure/Messages.pm   
(original)
+++ mod_parrot/branches/configure/lib/ModParrot/Configure/Messages.pm   Thu Jul 
24 12:05:56 2008
@@ -41,10 +41,7 @@
 mod_parrot Version $parrot_version Configure 1.0
 Copyright (C) 2008, Jeff Horwitz.
 
-Hello, I'm Configure. My job is to poke and prod your system to figure out
-how to build mod_parrot. The process is completely automated, unless you
-passed in the "--ask" flag on the command line, in which case you will be
-prompted for a few pieces of info.
+Determing your system configuration to figure out how to build mod_parrot.
 INTRODUCTION
 }
 
@@ -63,13 +60,7 @@
     my $make = shift;
     return <<CONCLUSION;
 
-Okay, we're done!
-
-You can now use `$make' to build your mod_parrot.
-After that, you can use `$make test' to run the test suite.
-
-Happy Hacking,
-        The mod_parrot Team
+Use "$make" to build mod_parrot, and use "$make test" to run the test suite.
 
 CONCLUSION
 }

<Prev in Thread] Current Thread [Next in Thread>
  • [svn:mod_parrot] r378 - mod_parrot/branches/configure/lib/ModParrot/Configure, particle <=