Adam Kennedy wrote:
> John Peacock wrote:
>> Adam Kennedy wrote:
>>> What does this mean for bugs though?
>>
>> But that's true of any new features of v5.10.0 that cannot be
>> backported to
>> maintperl.
>
> But what's true? :)
I mean that *any* new feature introduced in v5.10.0 could have bugs
Adam Kennedy wrote:
> What does this mean for bugs though?
But that's true of any new features of v5.10.0 that cannot be backported to
maintperl.
> If 5.005 can upgrade to blead functionality, but 5.10 can't, does that
> mean early 5.10 versions will have no recourse to being fixed?
Because blea
Adam Kennedy wrote:
> Can I ask the obvious question of why on earth you have a CPAN release
> that is incompatible with bleadperl?
The XS code that is in the CPAN release is C code in bleadperl core (and has
been since 5.9.1?). The CPAN release is intended only as a compatibility module
for earl
John Peacock wrote:
I need to mark the CPAN release of version.pm as being incompatible with
bleadperl, i.e. 5.9.0 or better, since version.pm is included in bleadperl. All
existing code is predicated on a minimum release, not a maximum release. What
I'm wondering is what shape should my code t
On Feb 3, 2007, at 12:15 PM, Eric Wilhelm wrote:
# from John Peacock
# on Saturday 03 February 2007 06:48 am:
existing code is predicated on a minimum release, not a maximum
release. What I'm wondering is what shape should my code take to
convey this behavior.
Hi John,
Can this not be spe
# from John Peacock
# on Saturday 03 February 2007 06:48 am:
>existing code is predicated on a minimum release, not a maximum
> release. What I'm wondering is what shape should my code take to
> convey this behavior.
Hi John,
Can this not be specified in the 'requires' field of the prereqs?
