[Pkg-parrot-devel] Parrot 4.0.0

[Alessandro Ghedini]

On Fri, Mar 23, 2012 at 02:06:32PM +0100, Alessandro Ghedini wrote:
> On Thu, Mar 22, 2012 at 04:11:27PM -0700, Allison Randal wrote:
> > On 03/22/2012 03:54 AM, Alessandro Ghedini wrote:
> > > 
> > > I have just tried to build nqp with 4.0.0 but it fails some tests
> > > because it needs ICU support. Would it be possible to enable ICU in
> > > Parrot (simply adding libicu-dev to Build-Depends should do)? I have
> > > tried it locally and everything seems to work fine with it.
> > 
> > Happy to do so. Note that ICU is a 33MB install dependency, which is a
> > significant addition to the size of a Parrot install. But, on most
> > Debian desktops/servers, this is tolerable. (It's mainly install media
> > and embedded environments that would struggle with the increase in size.)
> > 
> > In exchange, is there anything I can remove from the Parrot packages,
> > now that you're compiling nqp as a separate package rather than using
> > the (older) version bundled into Parrot? I understand that nqp still
> > uses the PCT libraries in Parrot, but that it might not use the PGE
> > libraries anymore? It certainly doesn't use the TGE libraries, never
> > did, so I probably will go ahead and remove those. Some of the other
> > libraries in the parrot-devel package are also suspiciously
> > Perl6-specific (like P6Regex and P6object), so if NQP/Rakudo aren't
> > using them any more, it doesn't make sense to keep them.
> 
> nqp and rakudo still need P6object, and, as for PGE, the only thing
> needed is Dumper AFAICT. Some of the nqp examples still use P6Regex
> and PGE though.
> 
> > > Also FYI, #641213 [0] is still valid (but it is nqp who needs those files
> > > now), not sure if you want to do anything about it.
> > > [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641213
> > 
> > I've mentioned that a general parrot-runtime package doesn't make sense
> > (these libraries don't really have anything to do with the Parrot
> > runtime, they're just optional pieces for language implementors). But I
> > could create specific binary packages for certain module sets. Like,
> > perhaps libpct-parrot for the PCT libraries, if you need it.
> 
> Yes that sounds good. Maybe having something like: libpct-parrot,
> libpge-parrot, another one for HLL, P6object and Regex (not sure how
> it may be called), etc.
> 
> Another thing, could you please add a
> 
>   Breaks: rakudo (<= 0.1~2011.07-1)
> 
> in the parrot package? This way parrot is not upgraded (and does not
> migrate to testing) until a new rakudo built with the new parrot is
> uploaded as well (rakudo hangs if it is run on a parrot different from
> the one it was built on).

Any news? Btw the Breaks should be "rakudo (<< 0.1~2012.01)" as per previous
discussion.

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.alioth.debian.org/pipermail/pkg-parrot-devel/attachments/20120406/75cbceba/attachment.pgp>