From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Racket: Move DrRacket to a separate output?
Date: Fri, 14 Sep 2018 10:49:06 +0200 [thread overview]
Message-ID: <87pnxgjwfx.fsf@gnu.org> (raw)
In-Reply-To: <87efdx6nzt.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 14 Sep 2018 00:17:42 +0200")
Hello Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Wouldn't it make sense to move DrRacket to a separate output? I take
> that most advanced users use something else (who said Emacs?) and
> DrRacket might eat up a decent amount of disk space + extra dependencies
> by itself.
I don’t think it’s a matter of being an “advanced” user or not (DrRacket
is really impressive, with a macro stepper and all sorts of bells and
whistles), but I agree with the rationale. :-)
> Arch Linux provides racket and racket-minimal: the latter is stripped
> from DrRacket:
>
> https://www.archlinux.org/packages/?q=racket
Such a split sounds good to me. What do Chris and other Racketeers
think?
Cheers,
Ludo’.
next prev parent reply other threads:[~2018-09-14 8:49 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 [this message]
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
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=87pnxgjwfx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).