On Sun, Apr 08, 2012 at 09:46:18AM -0700, Allison Randal wrote:
On 04/08/2012 09:29 AM, Alessandro Ghedini wrote:
If we go down the split to different libraries path, those libraries
should
depend on parrotapi-* too so that not only Parrot isn't updated but the
libraries aren't too.
What if we did something like bundling? Practically speaking, for at
least the foreseeable future, Rakudo requires Parrot and the primary
user of Parrot is Rakudo. Offering two separate packages for such a
closely-knit pair almost seems like a waste (it won't always be, but
let's be honest about
On Sat, Apr 07, 2012 at 07:12:19PM -0700, Allison Randal 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
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 + nqp + parrot + some Perl 6 modules, which may be nice
from a end user POV, but it's
Okay, instead of just complaining about this, I want to do something
about it. The Rakudo packages are so fragile on Debian, that they need
special constraints to make sure the Parrot packages are held back until
the Rakudo packages are updated.
So, why is Rakudo so dependent on one specific
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 -0400,
On 04/09/2012 09:10 PM, Alessandro Ghedini wrote:
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
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 + nqp +
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 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 don't
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 bundling
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 -0400,
On 4/7/2012 19:11, Allison Randal wrote:
Okay, instead of just complaining about this, I want to do something
about it. The Rakudo packages are so fragile on Debian, that they need
special constraints to make sure the Parrot packages are held back until
the Rakudo packages are updated.
So, why
On Sat, Apr 07, 2012 at 03:24:37PM -0700, Allison Randal wrote:
These are things that Rakudo shouldn't care about. A bug-fix or
performance enhancement in Parrot is good, but doesn't actually affect
Rakudo's ability to build or run.
Sometimes it does. See the flurry of difficulties we had
On Sat, Apr 07, 2012 at 07:12:19PM -0700, Allison Randal 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
15 matches
Mail list logo
