sound distribution practices

Alessandro Ghedini al3xbio at gmail.com
Sun Apr 8 17:32:55 UTC 2012


On Sun, Apr 08, 2012 at 12:15:44PM -0500, Patrick R. Michaud wrote:
> 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.

Well, I was talking about Rakudo Star. If I have a rakudo-star source package,
which includes the sources and builds packages for NQP, Rakudo and Parrot, then
if I need to do a change to the NQP packaging (which doesn't involve upstream
sources updates) I'd also have to reupload the whole source package, which in
turn means that not only NQP, but also Rakudo and Parrot would be rebuilt too.

(though I realized now that I may have missed the point of your comment).

Cheers

-- 
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20120408/2ef47c5b/attachment.asc>


More information about the parrot-dev mailing list