Well then, should I just put 0.30 in configure_requires?
Best,
David
Sent from my iPhone
On Sep 28, 2008, at 11:54, Eric Wilhelm <[EMAIL PROTECTED]>
wrote:
# from David E. Wheeler
# on Sunday 28 September 2008:
On Sep 28, 2008, at 10:48, Ken Williams wrote:
I don't see anything in our Changes file that explicitly addresses
this, perhaps it got fixed as a side effect of upgrades to
version.pm?
If so it would require spelunking through svn to figure it out. Do
you happen to have a one-liner that exhibits the behavior?
I think that Eric is actually intimately familiar with this issue.
http://www.mail-archive.com/module-build@perl.org/msg01416.html
No, that's a completely different thing that never left alpha.
Your original issue comes from installing 0.2808 on top of bleed
perl somehow -- however that manages to happen should now be fixed
by the fact that we have had a release. I suspect it has something
to do with 0.2808 not working with version.pm from bleed.
http://www.nntp.perl.org/group/perl.cpan.testers/2008/09/msg2307230.html
--Eric
--
So malloc calls a timeout and starts rummaging around the free chain,
sorting things out, and merging adjacent small free blocks into larger
blocks. This takes 3 1/2 days.
--Joel Spolsky
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
