Re: Bug#643469: ITP: nqp -- Not Quite Perl compiler
On Tue, Sep 27, 2011 at 10:21:11PM +0100, Allison Randal wrote:
> On 09/27/2011 06:39 PM, Alessandro Ghedini wrote:
> > On Tue, Sep 27, 2011 at 05:24:16PM +0100, Allison Randal wrote:
> > Quoting from the nqp README:
> >> is focused on being a high-level way to create compilers and libraries
> >> for virtual machines (such as the Parrot Virtual Machine)
> >
> > It doesn't really sound as intended *only* for Parrot (ok, as of now it
> > does support only parrot, but in the future this may change).
>
> The project leads have the intention to port it to other VMs. But,
> if/when they do, the packaging will need to distinguish between the
> libraries for Parrot and the libraries for other languages. Maybe the
> solution is a source package named nqp, with different binary packages
> libparrot-nqp, libmono-nqp, etc...
We would also need a "nqp" binary package that would ship the /usr/bin/nqp
executable (unless multiple executables will be added of course).
> It's worth talking to Patrick about his plans.
Agreed.
> > Also, aren't parrot-nqp and nqp different things? (parrot-nqp is currently
> > used to build nqp).
>
> NQP has been through several major refactors. This is just the latest
> one. It's a bootstrapping compiler, so using a version of itself to
> build itself is normal.
Sure, but we would need something to bootstrap it in the archive first.
I'm not really into bootstrapping compilers with themselves in Debian, but
having parrot-nqp in a different package would greatly ease this task (also
to avoid circular dependencies on nqp itself).
Cheers
--
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
Reply to: