unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Racket packages: formerly Move DrRacket to a separate output?
Date: Fri, 4 Oct 2019 10:46:58 -0500	[thread overview]
Message-ID: <20191004154658.5jswjutbcfe6zsig@thebird.nl> (raw)
In-Reply-To: <87bm90rn22.fsf@dustycloud.org>

What is the status of creating Racket packages. For a REST API server
I have two dependencies:

: raco pkg install https://github.com/dmac/spin.git
: raco pkg install https://github.com/BourgondAries/memo.git

what is the recommended way of packaging them in GNU Guix?

Pj.

On Fri, Sep 14, 2018 at 01:44:37PM -0400, Christopher Lemmer Webber wrote:
> Ludovic Courtès writes:
> 
> > 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’.
> 
> I'm ok with splitting out racket-minimal and racket, which is a common
> convention these days... even Racket's download page provides "Racket"
> and "Minimal Racket":
> 
> https://download.racket-lang.org/
> 
> I'd take the least effort route to doing that though... we aren't ready
> to break each of the Racket "core" packages into their own packages and
> I don't think that would need to hold this back.
> 
>  - Chris
> 
> 
> 

  reply	other threads:[~2019-10-04 15:53 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     ` Pjotr Prins [this message]
2019-10-04 19:23       ` Racket packages: formerly " 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=20191004154658.5jswjutbcfe6zsig@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).