[perl #38262] [CAGE] get external Perl5 modules out of the parrot repo

[Will Coleda via RT]

On Sun Mar 16 07:40:24 2008, coke wrote:
> On Sun, Mar 16, 2008 at 9:10 AM, James Keenan via RT
> <parrotbug-followup at parrotcode.org> wrote:
> > On Sun Mar 16 05:00:30 2008, bernhard wrote:
> >
> >  >
> >  > I'm reopening this ticket, as there are still external Perl 5 modules
> >  > in lib/Digest, lib/File, lib/IO, lib/Pod.
> >  >
> >  > The Perl::Critic policies in lib/Perl/Critic/Policy seem to be
> >  > Parrot-specific.
> >
> >  Barney,
> >
> >  I understood the point of the ticket to be to get rid of those Perl 5
> >  modules which were part of the Perl 5 core distribution (at least as of
> >  our minimum required version, 5.8.0).  So those modules that I
> >  eliminated -- e.g., Test::Builder, Test::More, Class::Struct -- were
> >  those that anyone with a typical Perl 5.8 would already have.
> >
> >  Those that remain -- e.g., File::Which, IO::CaptureOutput -- are
> >  *non-core*.  They are generally small enough that we include them in the
> >  Parrot distribution as a convenience to our users.
> >
> >  If my understanding is correct, then we can re-close the ticket.
> 
> The original ticket was to get *all* modules that were not
> parrot-specific out of core. I had just pointed out that many of these
> were an easy win. Let's leave the ticket open for now.
> 

Summing up an  IRC conversation with allison from today:

- Let's explicitly list which modules we are dual hosting from CPAN.
- building parrot (configure & make) shouldn't require anything outside of core perl.
- modules that are used for, e.g., 'make html' or other similar targets can be moved to the 
parrot developer bundle on CPAN.

-- 
Will "Coke" Coleda