From: Pjotr Prins <pjotr.public12@thebird.nl>
To: 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 06:44:20 -0600 [thread overview]
Message-ID: <20200220124420.fkmwlf3osp6otrlj@thebird.nl> (raw)
In-Reply-To: <878sky191q.fsf@dustycloud.org>
On Wed, Feb 19, 2020 at 05:55:45PM -0500, Christopher Lemmer Webber wrote:
> Am I right then that the challenge is less an "importer" from the Racket
> package repository and more to do with how Racket actually installs its
> package outputs? Or is it both?
At this stage a simple importer and adding packages by hand would work
for me. Recursive imports can be done later. Racket is typically not
as bad as Rust, Go or Javascript in wanting 100+ dependencies.
It would be great if we had a simple builder.
Pj.
next prev parent reply other threads:[~2020-02-20 12:51 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 [this message]
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=20200220124420.fkmwlf3osp6otrlj@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=cwebber@dustycloud.org \
--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).