From: Efraim Flashner <efraim@flashner.co.il>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 69283@debbugs.gnu.org
Subject: [bug#69283] [PATCH 2/3] guix: Remove rakudo-build-system.
Date: Sun, 25 Feb 2024 16:50:00 +0200 [thread overview]
Message-ID: <ZdtTmPr7Z6n2j9lc@3900XT> (raw)
In-Reply-To: <bcb72cab89a946544a87365d4d3914eb7e5a4bae.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
On Sat, Feb 24, 2024 at 02:27:45AM +0100, Liliana Marie Prikler wrote:
> 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?
That's a good question.
With the work that was done with the other patchset to adjust some of
the perl6 packages to become raku packages I don't believe any changes
were needed to the rakudo-build-system other than adjusting the check
phase. I'm glad that there weren't any problems with it, but I haven't
looked at either the language or the build system in more than 4 years.
I'd rather yank it out than dive in and make sure it works correctly, so
we're not leaving broken bits around if someone later wanted to use it,
but I don't know if they'd prefer a build system that probably mostly
works or to know that rakudo is packaged and they're on their own for
actual packages.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-25 14:52 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
2024-02-25 14:50 ` Efraim Flashner [this message]
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=ZdtTmPr7Z6n2j9lc@3900XT \
--to=efraim@flashner.co.il \
--cc=69283@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
/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.