On Sat Sep 01 02:55:28 2007, [EMAIL PROTECTED] wrote:
> > On Fri, 31 Aug 2007 17:47:56 -0700, James Keenan (via RT)
> <[EMAIL PROTECTED]> said:
>
> > In order to continue as a Parrot developer, do I really need to
> > perform yet another upgrade of Module::Build or Pod::Simple
> (distros
>
On Sep 1, 2007, at 12:19 PM, Sartak wrote:
On 8/31/07, via RT James Keenan <[EMAIL PROTECTED]>
wrote:
What is there to prevent us from configuring Bundle::Parrot as
specifying *minimum* versions of modules rather than the *latest*
versions thereof?
It isn't easy to find the minimum version
On 8/31/07, via RT James Keenan <[EMAIL PROTECTED]> wrote:
> What is there to prevent us from configuring Bundle::Parrot as
> specifying *minimum* versions of modules rather than the *latest*
> versions thereof?
It isn't easy to find the minimum version that works. If you find that
whatever versio
> On Fri, 31 Aug 2007 17:47:56 -0700, James Keenan (via RT) <[EMAIL
> PROTECTED]> said:
> In order to continue as a Parrot developer, do I really need to
> perform yet another upgrade of Module::Build or Pod::Simple (distros
> for which I have little use)? More to the point, is
On Fri Aug 31 17:47:56 2007, [EMAIL PROTECTED] wrote:
> Installing Bundle::Parrot this evening, I see that I am once again
> being force to upgrade to the latest version of some of its component
> modules -- almost certainly unnecessarily.
>
I was posting this RT as I was installing Bundle::P
# New Ticket Created by James Keenan
# Please include the string: [perl #45103]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45103 >
Installing Bundle::Parrot this evening, I see that I am once again
being force to upgr
