unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandru-Sergiu Marton <brown121407@posteo.ro>
To: 46352@debbugs.gnu.org
Cc: Alexandru-Sergiu Marton <brown121407@posteo.ro>
Subject: [bug#46352] [PATCH 0/4] Update Raku (Perl 6)
Date: Sat,  6 Feb 2021 23:33:32 +0200	[thread overview]
Message-ID: <20210206213332.11417-1-brown121407@posteo.ro> (raw)

Hi,

These patches update Rakudo, the Raku language compiler (formerly known as
Perl 6), to a newer version. I don't consider the work complete, because of a
few reasons:

* I didn't check if the perl6-* are compatible with this change;
* I didn't change the description/synopsis of what I updated;

yet the packages build and seem to work just fine.

I wanted to start a discussion before I go all-in on this.

Since the official name of the language is now Raku [1], should we rename the
module file to raku.scm? Also, in synopsis/description like the one for
Rakudo, where it says "Perl 6 Compiler", should we make it "Raku compiler"
instead? The website for Rakudo says it is "The most mature, production-ready
implementation of the Raku language." [2].

[1]: https://github.com/Raku/problem-solving/pull/89#issuecomment-541628893
[2]: https://rakudo.org/

Note that the rakudo package seems to be non-deterministic. The last version
was, and this new one is too.

Also note that I don't have any experience with Perl/Raku or Perl/Raku
tooling, so if I messed something up that should have been an obvious
Perl/Raku-related idiosyncrasy, please tell me.

Alexandru-Sergiu Marton (4):
  gnu: Add dyncall.
  gnu: moarvm: Update to 2020.12.
  gnu: nqp: Update to 2020.12.
  gnu: rakudo: Update to 2020.12.

 gnu/packages/c.scm     |  39 +++++++++++
 gnu/packages/perl6.scm | 144 ++++++++++++++++++++---------------------
 2 files changed, 109 insertions(+), 74 deletions(-)

-- 
2.30.0





             reply	other threads:[~2021-02-06 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 21:33 Alexandru-Sergiu Marton [this message]
2021-02-06 21:35 ` [bug#46352] [PATCH 1/4] gnu: Add dyncall Alexandru-Sergiu Marton
2021-02-06 21:35   ` [bug#46352] [PATCH 2/4] gnu: moarvm: Update to 2020.12 Alexandru-Sergiu Marton
2021-03-20 21:07     ` [bug#46352] [PATCH 0/4] Update Raku (Perl 6) Ludovic Courtès
2021-03-22  9:04       ` Alexandru-Sergiu Marton
2021-03-23 10:32         ` Ludovic Courtès
2021-02-06 21:35   ` [bug#46352] [PATCH 3/4] gnu: nqp: Update to 2020.12 Alexandru-Sergiu Marton
2021-03-20 21:10     ` [bug#46352] [PATCH 0/4] Update Raku (Perl 6) Ludovic Courtès
2021-02-06 21:35   ` [bug#46352] [PATCH 4/4] gnu: rakudo: Update to 2020.12 Alexandru-Sergiu Marton
2021-03-20 21:08     ` [bug#46352] [PATCH 0/4] Update Raku (Perl 6) Ludovic Courtès
2021-03-20 21:03   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210206213332.11417-1-brown121407@posteo.ro \
    --to=brown121407@posteo.ro \
    --cc=46352@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).