From: Guillaume Le Vaillant <glv@posteo.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 73056-done@debbugs.gnu.org
Subject: bug#73056: [PATCH 1/2] gnu: cl-ciel: Update to 0.2.1
Date: Sat, 07 Sep 2024 11:33:15 +0000 [thread overview]
Message-ID: <87le03y9z8.fsf@kitej> (raw)
In-Reply-To: <m1o751rmun.fsf@fastmail.net> (Konrad Hinsen's message of "Fri, 06 Sep 2024 14:24:48 +0200")
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Is building the core image useful, given that the sbcl-ciel-repl package
>> will contain the binary with the same included features?
>
> The CIEL REPL is specifically meant for use in the terminal, whereas the
> core image is recommended by upstream for use with Emacs/Slime and
> similar environments.
>
>> If yes, it would be better to put it in the "lib/" directory instead of
>> "bin/" (e.g. SBCL puts the default core image in "lib/sbcl/").
>
> I have no strong opinions on the location. There is only one other
> package in Guix that builds a core image. That's sbcl-slynk, and it
> puts the image under /bin, so I did the same.
>
> There is some justification to this choice because the images are
> actually executable. You can use either
>
> bin/ciel.image
>
> or
>
> sbcl --core bin/ciel.image
>
> with the same effect.
>
> As I said, I don't care much, but I think it would be preferable to have
> a uniform policy about this in Guix, now that we have two packages that
> build images :-)
>
> Cheers,
> Konrad.
Ok. Patch applied as 904f871378337b7c9e6ffa2b62d9a62a6d1e937d.
Thanks.
prev parent reply other threads:[~2024-09-07 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 19:42 [bug#73056] [PATCH 1/2] gnu: cl-ciel: Update to 0.2.1 Konrad Hinsen
2024-09-06 9:15 ` Guillaume Le Vaillant
2024-09-06 12:24 ` Konrad Hinsen
2024-09-07 11:33 ` Guillaume Le Vaillant [this message]
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=87le03y9z8.fsf@kitej \
--to=glv@posteo.net \
--cc=73056-done@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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.