[perl #41386] MANIFEST must die.

2007-05-12 Thread Allison Randal via RT
On Sun Feb 18 17:13:40 2007, coke wrote: > > If I'm understanding correctly: > > > > - MANIFEST indicates which files are to be in the distribution. > > > > - svn:ignore indicates which files in a build tree are to be > > ignored as part of "svn status" and other svn commands. > > > > - MANIFEST.

[perl #42898] [PATCH] src/library.c , honor PARROT_PREFER_SOURCE in extension guessing

2007-05-12 Thread Allison Randal via RT
Reverted in r18519. This feature is still being reviewed. (Previous patches implementing portions of this behavior may also be reverted.) Mike is writing a proposal for the mailing list to discuss. Allison

Re: [perl #42774] [PATCH] Configure.pl --gc=libc doesn't compile

2007-05-12 Thread Allison Randal
Andy Dougherty wrote: On Fri, 11 May 2007, Leopold Toetsch via RT wrote: Well, I saw some patches [1] floating by which did remove PObj_bufstart_external_FLAG. This flag was needed to sync the malloc-based allocators with parrots (and COWs) understanding of a 'not owned' / external buffer/str

Re: [PATCH] Re: [perl #42774] [PATCH] Configure.pl --gc=libc doesn't compile

2007-05-12 Thread Allison Randal
Andy Dougherty wrote: Here is a patch to get Configure.pl --gc=libc to at least compile again. Alas, it still doesn't seem to work. I'm getting various panics and crashes that usually (but not always) appear to be related to string stuff. I suspect I might not have Parrot_allocate_string() qui

[perl #42690] [TODO] optionally run configure/build tests during config process

2007-05-12 Thread James Keenan via RT
On Sat May 12 07:17:36 2007, jkeen at verizon.net wrote: > Applied with slight correction in r.. > That would be: r18516. kid51

[perl #42690] [TODO] optionally run configure/build tests during config process

2007-05-12 Thread James Keenan via RT
Applied with slight correction in r.. Correction was to place 2 tests in t/configure/25-options_test.t into SKIP blocks when $ENV {PERL5OPT}=-MDevel::Cover. This was necessary because Devel::Cover was gagging on running tests within tests. Tested in both trunk and reconfigure branch; resu

Re: [perl #42929] [BUG] t/doc/pod_todo.t: Massive failures from newly added test file

2007-05-12 Thread Paul Cochrane
James, Last night, I ran 'make test' and everything was cool. Tonight, I ran 'make test' and saw that a newly added test file, t/doc/ pod_todo.t, generated a massive number of lines of failure message. (See attached patch pod_todo.t.failure.txt.) I experienced these failures in both trunk and

Re: [perl #42929] [BUG] t/doc/pod_todo.t: Massive failures from newly added test file

2007-05-12 Thread Joshua Isom
On May 12, 2007, at 12:25 AM, chromatic wrote: I agree. It may be a decent test, but it's not a test to run by default right now. While I'm asking for a pony, I'd also like a way to disable the coding standards tests for an official release tarball. -- c This will at least take care of t