From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36131@debbugs.gnu.org
Subject: [bug#36131] Add Multiple Common Lisp Packages
Date: Tue, 25 Jun 2019 12:56:11 -0500 [thread overview]
Message-ID: <87zhm5k0qs.fsf@gmail.com> (raw)
In-Reply-To: <878stpllma.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 25 Jun 2019 17:39:57 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Hello Katherine,
>
> Thanks for this patch series!
You bet! Power to the Guix :)
> I’ve applied all of them until #7 included (fare-utils), fixing minor
> issues that ‘guix lint’ reported.
Thank you, and sorry for the linting issues. I get busy and then rushed
and I make these stupid mistakes.
> I’d be grateful if someone reading this could do their share of
> review/apply work! :-)
>
> I noticed that ‘ecl-hu.dwim.asdf’ and ‘ecl-rt’ fail to build, so I
> couldn’t test all the ‘ecl-*’ variants. Could you take a look at these
> two packages?
I focused on the SBCL packages and then retroactively went back and
added all the ECL packages, trying to be a good citizen. In retrospect,
this was not a good idea. Common Lisp code is not guaranteed to work
across runtimes.
If you're OK with it, I would just go ahead and delete any ECL package
that doesn't immediately work. I can do this myself, but I'm currently
on holiday and won't be able to take a look for another week and a half.
> More generally, does it make sense to have ECL variants for each and
> every package? Or should we trim that down? I’m under the impression
> that ECL is typically used with rather small code bases since it’s meant
> to be embedded, but then I’m not a Common Lisper.
I think ECL is used outside embedded contexts, but I haven't found a
reason to use it yet. If I remember correctly, I think one compiles
faster than the other, and the other runs faster, so some people switch
between the two when developing and then deploying.
--
Katherine
next prev parent reply other threads:[~2019-06-25 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 0:08 [bug#36131] Add Multiple Common Lisp Packages Katherine Cox-Buday
2019-06-25 15:39 ` Ludovic Courtès
2019-06-25 17:56 ` Katherine Cox-Buday [this message]
2019-06-26 8:56 ` [bug#36131] Removing some of the Common Lisp packages for ECL? Ludovic Courtès
2019-07-02 15:51 ` [bug#36131] Add Multiple Common Lisp Packages Ludovic Courtès
2020-01-03 20:14 ` bug#36131: " Guillaume Le Vaillant
2020-01-06 9:34 ` [bug#36131] " Ludovic Courtès
2020-01-06 12:06 ` Katherine Cox-Buday
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=87zhm5k0qs.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=36131@debbugs.gnu.org \
--cc=ludo@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 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.