[DRAFT] Parrot module ecosystem

[Timothy S. Nelson]

On Sun, 9 Aug 2009, Allison Randal wrote:

> I don't see anything here for "standard build instructions". As in, the 
> specific command-line instructions for "configure", "build", "test", and 
> "install". These could allow variable substitutions from parrot_config (or 
> Aviary's collected configuration information), so Rakudo's "perl 
> Configure.pl" could be "@perl@ Configure.pl", while Pynie's "python setup.py 
> build" could be "@python@ setup.py build", and a general 'make test' could be 
> "@make@ test" (to allow for nmake, etc).

 	Why not allow multiple lines for these, and call it as "script" :).

---------------------------------------------------------------------
| Name: Tim Nelson                 | Because the Creator is,        |
| E-mail: wayland at wayland.id.au    | I am                           |
---------------------------------------------------------------------

----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- 
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----