From: Charles via Guix-patches via <guix-patches@gnu.org>
To: 68859@debbugs.gnu.org
Cc: Charles <charles@charje.net>,
Guillaume Le Vaillant <glv@posteo.net>,
Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
jgart <jgart@dismail.de>
Subject: [bug#68859] [PATCH v2] gnu: Add cl-modf.
Date: Wed, 31 Jan 2024 18:29:22 -0600 [thread overview]
Message-ID: <56e554151a26bd59da3fb75e94a6b9f84c1ed12a.1706747362.git.charles@charje.net> (raw)
In-Reply-To: <bf39e305ae16297dff4ad59c5b59cc886783c359.1706745487.git.charles@charje.net>
* gnu/packages/lisp-xyz.scm (sbcl-modf, cl-modf, ecl-modf): New variables.
Change-Id: Ic7e8e4511ca537531a7d9aa134e671aca060aa09
---
I just saw that you change the git-file-name to use the package name, so I updated this patch to do the same.
gnu/packages/lisp-xyz.scm | 36 ++++++++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index b764d6b885..8c9ee783a4 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -11552,6 +11552,42 @@ (define-public ecl-fset
;; Tests fails on ECL with "The function FSET::MAKE-CHAR is undefined".
'(#:tests? #f))))
+(define-public sbcl-modf
+ (let ((commit "dea93fe62c6bf7f66f32f52ac0c555aedbf7abad")
+ (revision "0"))
+ (package
+ (name "sbcl-modf")
+ (version (git-version "0" revision commit))
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/smithzvk/modf")
+ (commit commit)))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32
+ "1aap7ldy7lv942khp026pgndgdzfkkqa9xcq1ykinrmflrgdazay"))))
+ (build-system asdf-build-system/sbcl)
+ (inputs
+ (list sbcl-alexandria
+ sbcl-closer-mop
+ sbcl-iterate))
+ (native-inputs
+ (list sbcl-stefil))
+ (home-page "https://github.com/smithzvk/modf")
+ (synopsis "@code{setf} like macro for functional programming in Common Lisp")
+ (description "This library simplifies functional programming in Common
+Lisp by making it easier to make new data structures with specified changes in
+place.")
+ (license license:bsd-3))))
+
+(define-public cl-modf
+ (sbcl-package->cl-source-package sbcl-modf))
+
+(define-public ecl-modf
+ (sbcl-package->ecl-package sbcl-modf))
+
(define-public sbcl-cl-cont
(let ((commit "fc1fa7e6eb64894fdca13e688e6015fad5290d2a")
(revision "1"))
base-commit: bf7991a8c767abd32cfb2c92e3d57665a7cabf00
prerequisite-patch-id: bcaf8eb7f369a54bf47e9c7ef7b94fda2295de4a
--
2.41.0
next prev parent reply other threads:[~2024-02-01 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 23:58 [bug#68859] [PATCH] gnu: Add cl-modf Charles via Guix-patches via
2024-02-01 0:29 ` Charles via Guix-patches via [this message]
2024-02-05 13:37 ` bug#68859: [PATCH v2] " 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=56e554151a26bd59da3fb75e94a6b9f84c1ed12a.1706747362.git.charles@charje.net \
--to=guix-patches@gnu.org \
--cc=68859@debbugs.gnu.org \
--cc=charles@charje.net \
--cc=cox.katherine.e+guix@gmail.com \
--cc=glv@posteo.net \
--cc=jgart@dismail.de \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
/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).