On Sun, Apr 08, 2012 at 08:42:21PM +0200, Moritz Lenz wrote:
> On 04/08/2012 06:53 PM, Alessandro Ghedini wrote:
> > On Sun, Apr 08, 2012 at 11:09:30AM -0500, Patrick R. Michaud wrote:
> >> On Sun, Apr 08, 2012 at 03:23:26PM +0200, Alessandro Ghedini wrote:
> >> > On Sat, Apr 07, 2012 at 09:08:21PM
On 04/08/2012 06:53 PM, Alessandro Ghedini wrote:
> On Sun, Apr 08, 2012 at 11:09:30AM -0500, Patrick R. Michaud wrote:
>> On Sun, Apr 08, 2012 at 03:23:26PM +0200, Alessandro Ghedini wrote:
>> > On Sat, Apr 07, 2012 at 09:08:21PM -0400, Andrew Whitworth wrote:
>> > Btw, this also applies to NQP b
On Sun, Apr 08, 2012 at 07:32:55PM +0200, Alessandro Ghedini wrote:
> On Sun, Apr 08, 2012 at 12:15:44PM -0500, Patrick R. Michaud wrote:
> > 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
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
On Sun, Apr 08, 2012 at 03:23:26PM +0200, Alessandro Ghedini wrote:
> On Sat, Apr 07, 2012 at 09:08:21PM -0400, Andrew Whitworth wrote:
> > What if we did something like bundling?
>
> Isn't this what Rakudo Star does? AFAICT the Star "distribution" is nothing
> more
> than a bundle of rakudo + nq
I just sent the message below to the parrot packagers mailing
list on Debian; I felt it was also worth sharing with p6c.
I'm certain there are people who disagree greatly with what
I wrote -- and that's fine -- I just wanted to make sure my
current perspective on this topic was available to p6c as
