From: "Ludovic Courtès" <ludo@gnu.org>
To: Dimakakos Dimos <bendersteed@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Racket packages: formerly Move DrRacket to a separate output?
Date: Sun, 06 Oct 2019 14:34:44 +0200 [thread overview]
Message-ID: <87o8yudpcr.fsf@gnu.org> (raw)
In-Reply-To: <877e5k1671.fsf@gmail.com> (Dimakakos Dimos's message of "Sat, 05 Oct 2019 01:44:50 +0300")
Hi!
Dimakakos Dimos <bendersteed@gmail.com> skribis:
> Christopher Lemmer Webber writes:
>
>> I think nobody has written a Racket importer. I have it as a
>> longstanding background TODO task but clearly haven't found the
>> time... despite the fact that I desperately want the feature.
>
> I could start working on this, starting tomorrow. I will need a bit of
> guidance though, shall I open a new thread or use this one?
That’d be great! You can ask for guidance here and on #guix on
irc.freenode.net (and #racket I guess!).
I guess it should be rather easy. You can look at the existing
importers in (guix import crate), (guix import pypi), etc.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-10-06 12:34 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 [this message]
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
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
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=87o8yudpcr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bendersteed@gmail.com \
--cc=guix-devel@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).