all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>, 69283@debbugs.gnu.org
Subject: [bug#69283] [PATCH 2/3] guix: Remove rakudo-build-system.
Date: Sat, 24 Feb 2024 02:27:45 +0100	[thread overview]
Message-ID: <bcb72cab89a946544a87365d4d3914eb7e5a4bae.camel@gmail.com> (raw)
In-Reply-To: <0d38a55be8a40b591a7846d013b957702d6b2145.1708411903.git.efraim@flashner.co.il>

Am Dienstag, dem 20.02.2024 um 09:03 +0200 schrieb Efraim Flashner:
> * guix/build/rakudo-build-system.scm: Remove file.
> * guix/build-system/rakudo.scm: Remove file.
> * doc/guix.texi (Build Systems): Remove section for rakudo-build-
> system.
> * etc/snippets/yas/scheme-mode/guix-package: Remove rakudo-build-
> system.
> * Makefile.am (MODULES): Remove rakudo-build-system files.
> 
> Change-Id: Ida6ec6c9be075f10be540c82cee5207176f1cfe2
> ---
Given that we will keep raku, but not "perl6", what is the impact on
packaging raku packages after this removal?  Will we have to reinvent
rakudo-build-system?

Cheers




  reply	other threads:[~2024-02-24  1:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20  7:01 [bug#69283] [PATCH 0/3] Remove perl6 packages Efraim Flashner
2024-02-20  7:03 ` [bug#69283] [PATCH 1/3] gnu: " Efraim Flashner
2024-02-20  7:03 ` [bug#69283] [PATCH 2/3] guix: Remove rakudo-build-system Efraim Flashner
2024-02-24  1:27   ` Liliana Marie Prikler [this message]
2024-02-25 14:50     ` Efraim Flashner
2024-02-25 16:46       ` Liliana Marie Prikler
2024-02-20  7:03 ` [bug#69283] [PATCH 3/3] gnu: perl6.scm: Rename to rakudo.scm Efraim Flashner
     [not found] ` <handler.69283.B.170841250817104.ack@debbugs.gnu.org>
2024-03-05  8:21   ` bug#69283: Acknowledgement ([PATCH 0/3] Remove perl6 packages.) Efraim Flashner

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

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

  git send-email \
    --in-reply-to=bcb72cab89a946544a87365d4d3914eb7e5a4bae.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=69283@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.