sound distribution practices

[Patrick R. Michaud]

On Sun, Apr 08, 2012 at 06:53:49PM +0200, Alessandro Ghedini wrote:
> On Sun, Apr 08, 2012 at 11:09:30AM -0500, Patrick R. Michaud wrote:
> > Unfortunately, aiui Parrot's current implementation requires that 
> > all of its downstream users (including Rakudo and NQP) must be 
> > rebuilt every time Parrot is changed.  Bytecode files created for one 
> > version of Parrot cannot be directly used with a later version of 
> > Parrot -- they must be regenerated.
> 
> This is true for newer upstream Parrot releases, but it happens that Debian
> packages require new uploads only to do Debian-specific changes (e.g. changes to
> the packaging, small patches to the upstream code, ...) and the need to rebuild
> Rakudo, NQP *and* Parrot just because I need to do a small change to the packaging
> of, say, NQP is just putting more unnecessary burden on the Debian
> infrastructure (build daemons, ftp master, mirrors, ...).

I'm not quite able to follow here -- could you explain further or give
an example?  I mean, I understand how changes to NQP can affect
Rakudo, but I don't understand why/how it affects Parrot.

Pm