Re: MANIFEST.SKIP mandatory?

2009-11-21 Thread David Golden
I take patches... Otherwise, please just be patient. David On Nov 21, 2009 11:17 AM, "Zefram" wrote: David Golden wrote: >I don't want someone to "Build manifest" and add it by mistake. Maybe "./Build manifest" needs some new logic, then. Not distclean. -zefram

Re: MANIFEST.SKIP mandatory?

2009-11-21 Thread Zefram
David Golden wrote: >I don't want someone to "Build manifest" and add it by mistake. Maybe "./Build manifest" needs some new logic, then. Not distclean. -zefram

Re: MANIFEST.SKIP mandatory?

2009-11-21 Thread David Golden
I don't want someone to "Build manifest" and add it by mistake. Once its added to the default in EU::Manifest, I'll make that a prereq and we're done. Progress is a bitch, eh? David On Nov 21, 2009 10:48 AM, "Zefram" wrote: David Golden wrote: >I'll sort it out. Now that we have MYMETA files w

Re: MANIFEST.SKIP mandatory?

2009-11-21 Thread Zefram
David Golden wrote: >I'll sort it out. Now that we have MYMETA files we need to be sure they >don't get packed up in a dist. The contents of the distribution is controlled by MANIFEST. There's no new reason to use SKIP files here. -zefram

Re: MANIFEST.SKIP mandatory?

2009-11-21 Thread David Golden
I'll sort it out. Now that we have MYMETA files we need to be sure they don't get packed up in a dist. Perhaps MANIFEST.SKIP isn't the way to do it, or maybe we need to just clean up generated SKIP files. There is a patch for EU::Manifest to add MYMETA to the default skip list, but I don't think i

MANIFEST.SKIP mandatory?

2009-11-21 Thread Zefram
I don't use a MANIFEST.SKIP. Using Module::Build 0.35_09 (from the Perl 5.11.2 distribution), "./Build distclean" generates a MANIFEST.SKIP (1197 bytes) and MANIFEST.SKIP.bak (251 bytes), and then complains about the former not being in MANIFEST. This seems to run contrary to the "clean" part of

Re: bleadperl and bootstrapping based on Module::Build

2009-11-21 Thread David Golden
I found the problem and it should now be fixed in blead. Unfortunately, too late for 5.11.2, but with a monthly release cycle, we'll soon be back on track. When dual-core modules moved to the cpan/ directory in the Perl source tree, the idea was in part that updating them would be a matter of just