[Pkg-parrot-devel] Parrot 4.0.0

[Allison Randal]

On 04/06/2012 10:16 AM, Dominique Dumont wrote:
> Le Friday 6 April 2012 12:23:11, Alessandro Ghedini a écrit :
>>> in the parrot package? This way parrot is not upgraded (and does not
>>> migrate to testing) until a new rakudo built with the new parrot is
>>> uploaded as well (rakudo hangs if it is run on a parrot different from
>>> the one it was built on).
>>
>> Any news? Btw the Breaks should be "rakudo (<< 0.1~2012.01)" as per
>> previous discussion.
> 
> Given that this thread started 3 months ago, I think you should implement your 
> ideas unless Allison replies within next week.

As long as we upload the parrot and rakudo packages at the same time, we
should be fine. Strategies using Breaks are too fragile to be worth the
complexity. (And, none of this would be necessary if Rakudo didn't poke
so indiscriminately into Parrot internals.)

> If some changes are required afterwards, a new package release is always 
> possible.
> 
> I'm afraid that, if we delay longer, wheezy will ship an old parrot and 
> rakudo. That would be a shame.

Do any of you have DD status? I'm DM for Parrot, but can't actually
upload the packages because libparrot is always "NEW". Like I said, the
4.0.0 packages are ready to go, they just need a sponsor.

Allison