sound distribution practices

[Andrew Whitworth]

That solution is fine by me. The real source of the problem is on the
Parrot side, and our extremely fragile versioning system for bytecode.
This is something that we need to address to help fix the problem in
the long term.

Exactly how we fix it is a matter for discussion, of course.

--Andrew Whitworth



On Sat, Apr 7, 2012 at 10:12 PM, Allison Randal <allison at parrot.org> wrote:
> Patrick and I just chatted on the phone, here's a summary of the working
> scenario we reached:
>
> - Rakudo will deliver a Rakudo release for each supported ("stable")
> Parrot release, a few days after the Parrot release.
>
> - Debian will package each supported release of Parrot.
>
> Debian packages for Rakudo will either:
>
> - Rebuild the old Rakudo packages on the new Parrot packages (since the
> old compiled bytecode, etc won't work on a different version of Parrot), or
>
> - Package the new version of Rakudo at exactly the same time as the new
> version of Parrot. Define the version requirements so tightly (=) that
> the Rakudo packages require exactly one version of Parrot.
>
> The first alternative is better, and will be the first preference. But
> it needs stable APIs from Parrot, so old Rakudo packages consistently
> work on newer versions of Parrot. This is mostly working, but the
> exceptions are pain points for packaging (we've got one coming up for 4.3).
>
> Allison
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev