On 8/14/07, James E Keenan <[EMAIL PROTECTED]> wrote: > Paul Cochrane wrote: > > On 14/08/07, Joshua Hoblitt <[EMAIL PROTECTED]> wrote: > >> Why not just pull Slurp or File::Slurp into the tree? Yes, writing a > >> slurp function is trivial but (bare with me here) if it's non-trivial > >> enough to be factored out into a module then it should be non-trivial > >> enough to not re-invent the wheel. > > > > Agreed. Why not just make it part of Bundle::Parrot? > > > > To be honest, this is the first that I've heard of Bundle::Parrot. I > cannot locate any postings to the mailing list since last November > containing 'Bundle' in its subject line. > > But the fact that I've been able to work on Parrot since last November > *without* having installed Bundle::Parrot indicates that we make some > distinction between that non-core Perl 5 functionality we want *in* the > Parrot distribution and that which is found in Bundle::Parrot. > > Could you clarify how that distinction is made? > i started Bundle::Parrot to work towards the goal of removing all external modules from the parrot repository. external modules don't belong in the repository unless we need to fork them from their CPAN version. unfortunately, this work has not been completed.
the idea is that anybody who wants to develop parrot can install Bundle::Parrot from CPAN, and then run through the config/build/test cycle without requiring any other modules. this requires that Bundle::Parrot contain all necessary modules for those tasks. however, it does not require that every nifty module that might in some way benefit parrot should be added to Bundle::Parrot--we're trying to keep this distro (and requirements for developing parrot) lightweight. work to be done involves assessing what modules are missing from Bundle::Parrot and adding them. also, testing config/build/test and other development tasks with only core perl and Bundle::Parrot--removing external modules contained in the parrot repository. documentation somewhere inside the parrot repository should mention Bundle::Parrot and how to get it once it's truly required. although i started the work, all of the parrot release managers share co-maintainership, so no one person should be a bottleneck if patches are submitted via parrotbug. ~jerry
