On Tue, Mar 25, 2008 at 7:34 PM, James Keenan via RT <[EMAIL PROTECTED]> wrote: > On Fri Mar 21 19:23:13 2008, [EMAIL PROTECTED] wrote: > > No, and it appears not be part of Bundle::Parrot on CPAN, either. We'll > > have to rectify this. > > > > Coke asked me to pose this question for general discussion: > > If individual languages -- as distinct from Parrot itself -- require > non-core modules from CPAN, should such modules go into Bundle::Parrot? > Should we create a Bundle::Parrot::Languages? Should we create a > Bundle::Parrot::SomeSpecificLanguage? > no, definitely not. languages must be self-contained. that means any modules/libraries necessary for a particular language implementation must be checked for by the language itself, and not by parrot. languages/dotnet gets this right, by having its own Configure.pl. other languages must move to that standard.
Bundle::Parrot is for perl modules that are required to build and develop parrot core, and parrot core only. ~jerry
