From: Guillaume Le Vaillant <glv@posteo.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 73057@debbugs.gnu.org
Subject: [bug#73057] [PATCH 2/2] gnu: Add sbcl-ciel-repl.
Date: Fri, 06 Sep 2024 09:25:47 +0000 [thread overview]
Message-ID: <871q1xjfqc.fsf@kitej> (raw)
In-Reply-To: <m1ed5xga34.fsf@fastmail.net> (Konrad Hinsen's message of "Thu, 05 Sep 2024 21:43:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
> index c22d5f6565..536b4029dc 100644
> --- a/gnu/packages/lisp-xyz.scm
> +++ b/gnu/packages/lisp-xyz.scm
> @@ -3563,6 +3563,75 @@ (define-public cl-ciel
> (define-public ecl-ciel
> (sbcl-package->ecl-package sbcl-ciel))
>
> +(define-public sbcl-ciel-repl
> + (let ((commit "0b26d64dcd91a3a2aa962842629a853261dd30fe")
> + (version "0.2.1"))
> + (package
> + (name "sbcl-ciel-repl")
> + (version version)
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/khinsen/CIEL")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32 "0gm8slnz4jw98rkijnh2dp6x629xdnfk8z7j35g03j6ypr56v06h"))
> + (patches (search-patches "ciel-repl.patch"))))
Is there a reason to take the sources from
<https://github.com/khinsen/CIEL> instead of the upstream repository at
<https://github.com/ciel-lang/CIEL>?
The "ciel-repl.patch" referenced in the 'source' field is missing.
Could you send an updated patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-09-06 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 19:43 [bug#73057] [PATCH 2/2] gnu: Add sbcl-ciel-repl Konrad Hinsen
2024-09-06 9:25 ` Guillaume Le Vaillant [this message]
2024-09-06 12:26 ` Konrad Hinsen
2024-09-06 12:27 ` Konrad Hinsen
2024-09-07 11:35 ` bug#73057: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q1xjfqc.fsf@kitej \
--to=glv@posteo.net \
--cc=73057@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.