Front page | perl.perl5.porters |
Postings from August 2008
On Wed, Aug 27, 2008 at 04:05:38PM -0400, Jerry D. Hedden wrote: > In perltodo.pod, it reads: > > Bundle dual life modules in ext/ > For maintenance (and branch merging) reasons, it would be useful to move > some architecture-independent dual-life modules from lib/ to ext/, if > this has no negative impact on the build of perl itself. > > However, we need to make sure that they are still installed in > architecture-independent directories by "make install". Oh. I might have failed on that bit. > I assume that Nick's moving Test::Harness under ext/ was a case of 'it > would be useful'. How can one tell if a module meets that criterion? Well, it was very specifically "Parallel tests aren't working quite correctly, and it's way easier to play if I can swap out the 3.13 release and drop in the svn HEAD, particularly given that I have commit on it" > For example, should Thread::Queue and Thread::Semaphore be moved? > (I'm asking because I maintain them.) I thought that the ultimate plan was everything dual life that can be. But Rafael added the text including the "some", so there may be something I have forgotten. I'm quite happy to shift them around with perforce, but everyone else with commit seems to be happier to defer the faff until git. Nicholas ClarkThread Previous