On 8/14/07, Joshua Hoblitt <[EMAIL PROTECTED]> wrote: > On Tue, Aug 14, 2007 at 07:11:36AM -0700, jerry gay wrote: > > 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. > > Particle++ > thanks. it's nothing, really, CPAN Bundles magically contain precisely zero lines of code.
> > 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. > > ~/parrot $ grep -iR Parrot::Bundle docs > (notta) > yep, that's TBD. i'm pretty sure there's an RT ticket... but i can't find it. maybe it's been closed off. the ticket likely didn't specifically mention documentation anyway. > I think we should just change the install docs now to say the installing > Parrot::Bundle is a prereq to building Parrot and that the bundle will > need to be reinstalled periodically (perhaps we could add a test to check > for the right versions of modules to be installed). > > > 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. > > A pointer to where the source code lives would be nice. ;) > the cpan tarball is the entire source. however, if you prefer svn access, you can get it at googlecode: http://bundle-parrot.googlecode.com/svn/trunk/ thanks for helping me fill in the bits i missed earlier. ~jerry
