From: "Andreas J. Koenig" To: jesse <[EMAIL PROTECTED]> Cc: Leopold Toetsch, Allison Randall Subject: Re: Pod::Simple::Text Date: Sun, 08 Jan 2006 11:57:34 +0100
For various reasons, CPAN knows Parrot as the canonical owner of a whole slew of CPAN modules that are bundled with it. This isn't quite right. For the future, Parrot needs a META.yml to ignore these modules AND we need to get Andreas a list of them so that he can sort out the PAUSE. Best, Jesse >>>>> On Sun, 8 Jan 2006 05:08:38 -0500, jesse <[EMAIL PROTECTED]> said: > On Sat, Jan 07, 2006 at 12:08:37PM +0100, Leopold Toetsch wrote: >> >> On Jan 6, 2006, at 23:07, jesse wrote: >> >> >Parrot 0.40 is coming up as the canonical source of Pod::Simple::Text. >> >> When I started as pumpking and had uploaded the first parrot, I got all >> possible (of course) failing automatic test results. I mailed with some >> CPAN folks, what we could do that the indexer and whatnot just ignores >> parrot. I was told there is no solution and eventually gave up. > Apparently, this is what needs to end up in a distribution's META.yml to stop > it from being treated as the canonical source for things in those directories. > no_index: > directory: > - ex > - inc > - t Yes, this is what we have today and probably didn't have when Leo asked for the first time whan can be done about it. > I don't know exactly what we should do about existing dists. I can inject some cleanup SQL into the database. I need to know which namespaces should not be treated as belonging to parrot. CPAN/modules/02packages.details.txt.gz lists ~200 namespaces in various parrot distros. Can anybody tell me which I should clean out? -- andreas --
