From: Guillaume Le Vaillant <glv@posteo.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 73056@debbugs.gnu.org
Subject: [bug#73056] [PATCH 1/2] gnu: cl-ciel: Update to 0.2.1
Date: Fri, 06 Sep 2024 09:15:59 +0000 [thread overview]
Message-ID: <875xr9jg6o.fsf@kitej> (raw)
In-Reply-To: <m1h6atga4z.fsf@fastmail.net> (Konrad Hinsen's message of "Thu, 05 Sep 2024 21:42:36 +0200")
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
> index 64ffd93e60..c22d5f6565 100644
> --- a/gnu/packages/lisp-xyz.scm
> +++ b/gnu/packages/lisp-xyz.scm
> @@ -3462,20 +3462,20 @@ (define-public ecl-chunga
> (sbcl-package->ecl-package sbcl-chunga))
>
> (define-public sbcl-ciel
> [...]
> + (outputs '("out" "image"))
> + (arguments
> + (list
> + #:phases
> + #~(modify-phases %standard-phases
> + (add-after 'create-asdf-configuration 'build-image
> + (lambda* (#:key outputs #:allow-other-keys)
> + (build-image
> + (string-append (assoc-ref outputs "image") "/bin/ciel")
> + outputs
> + #:dependencies '("ciel")))))))
> (home-page "http://ciel-lang.org/")
> (synopsis "CIEL Is an Extended Lisp")
> (description
Hi.
Is building the core image useful, given that the sbcl-ciel-repl package
will contain the binary with the same included features?
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/").
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-09-06 12:06 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 [this message]
2024-09-06 12:24 ` Konrad Hinsen
2024-09-07 11:33 ` bug#73056: " Guillaume Le Vaillant
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=875xr9jg6o.fsf@kitej \
--to=glv@posteo.net \
--cc=73056@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 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).