From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Racket packages: formerly Move DrRacket to a separate output?
Date: Thu, 20 Feb 2020 14:32:35 +0100 [thread overview]
Message-ID: <87v9o15qq4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20200220124420.fkmwlf3osp6otrlj@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
At first glance, I don't think the builder would be too hard.
On a related note, installing racket-minimal, then running
--8<---------------cut here---------------start------------->8---
raco pkg install drracket
--8<---------------cut here---------------end--------------->8---
works except for the package that bind against glib and cannot find it.
So when we make the racket build system, we must ensure the bindings are
properly patched in.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-20 13:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 22:17 Racket: Move DrRacket to a separate output? Pierre Neidhardt
2018-09-14 8:49 ` Ludovic Courtès
2018-09-14 17:44 ` Christopher Lemmer Webber
2019-10-04 15:46 ` Racket packages: formerly " Pjotr Prins
2019-10-04 19:23 ` Christopher Lemmer Webber
2019-10-04 20:54 ` Pjotr Prins
2019-10-04 22:44 ` Dimakakos Dimos
2019-10-05 7:50 ` Gábor Boskovits
2019-10-05 12:34 ` Christopher Lemmer Webber
2019-10-05 18:51 ` Dimakakos Dimos
2019-10-05 12:39 ` Pierre Neidhardt
2019-10-06 12:34 ` Ludovic Courtès
2020-02-18 16:07 ` Pierre Neidhardt
2020-02-19 19:55 ` Dimakakos Dimos
2020-02-19 22:55 ` Christopher Lemmer Webber
2020-02-20 12:44 ` Pjotr Prins
2020-02-20 13:32 ` Pierre Neidhardt [this message]
2020-02-20 21:59 ` Pjotr Prins
2020-07-08 12:35 ` Christopher Lemmer Webber
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=87v9o15qq4.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.