From: cage <cage-dev@twistfold.it>
To: 46891@debbugs.gnu.org
Subject: [bug#46891] [PATCH 3/9] - added cl-access.
Date: Wed, 3 Mar 2021 16:22:13 +0100 [thread overview]
Message-ID: <YD+ppS8sj5i0Atg0@kurosawa.casa.net> (raw)
---
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 6238f6133a..2a1bf6a7b1 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -14857,3 +14857,39 @@ protocol for Mastodon.")
(define-public cl-spark
(sbcl-package->cl-source-package sbcl-cl-spark))
+
+(define-public sbcl-cl-access
+ (let ((commit "1b26db3760018cdc4624f880f0a1e0155d8f6c50")
+ (revision "1"))
+ (package
+ (name "sbcl-cl-access")
+ (version (git-version "1.5.0" revision commit))
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/sharplispers/access")
+ (commit commit)))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "1knd3n4mpzkc97i1znbas32pscd30416isvmx2pjmgvar6k93pl5"))))
+ (build-system asdf-build-system/sbcl)
+ (arguments
+ '(#:asd-systems '("access")))
+ (inputs
+ `(("sbcl-lisp-unit2" ,sbcl-lisp-unit2)
+ ("sbcl-iterate" ,sbcl-iterate)
+ ("sbcl-closer-mop" ,sbcl-closer-mop)
+ ("sbcl-alexandria" ,sbcl-alexandria)
+ ("sbcl-anaphora" ,sbcl-anaphora)
+ ("sbcl-interpol" ,sbcl-cl-interpol)))
+ (synopsis "Common lisp library to unify access to dictionary-like data-structures")
+ (description "Common lisp library to unify access to dictionary structures ")
+ (home-page "https://github.com/sharplispers/access")
+ (license license:bsd-3))))
+
+(define-public ecl-cl-access
+ (sbcl-package->ecl-package sbcl-cl-access))
+
+(define-public cl-access
+ (sbcl-package->cl-source-package sbcl-cl-access))
--
2.30.1
next reply other threads:[~2021-03-03 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:22 cage [this message]
2021-03-04 10:20 ` [bug#46891] [PATCH 3/9] - added cl-access 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=YD+ppS8sj5i0Atg0@kurosawa.casa.net \
--to=cage-dev@twistfold.it \
--cc=46891@debbugs.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 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).