From: Ricardo Wurmus <rekado@elephly.net>
To: 27132@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#27132: [PATCH 4/6] gnu: Add sbcl-iterate.
Date: Mon, 29 May 2017 19:21:29 +0200 [thread overview]
Message-ID: <20170529172131.20954-4-rekado@elephly.net> (raw)
In-Reply-To: <20170529172131.20954-1-rekado@elephly.net>
* gnu/packages/lisp.scm (sbcl-iterate): New variable.
---
gnu/packages/lisp.scm | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index 240c1b27f..669005d24 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -1273,3 +1273,31 @@ the string into one of the standard Common Lisp number types, if possible, or
else @code{parse-number} signals an error of type @code{invalid-number}.")
(license license:bsd-3)))
+(define-public sbcl-iterate
+ (package
+ (name "sbcl-iterate")
+ ;; The latest official release (1.4.3) fails to build so we have to take
+ ;; the current darcs tarball from quicklisp.
+ (version "20160825")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (string-append "http://beta.quicklisp.org/archive/iterate/"
+ "2016-08-25/iterate-"
+ version "-darcs.tgz"))
+ (sha256
+ (base32
+ "0kvz16gnxnkdz0fy1x8y5yr28nfm7i2qpvix7mgwccdpjmsb4pgm"))))
+ (build-system asdf-build-system/sbcl)
+ (home-page "https://common-lisp.net/project/iterate/")
+ (synopsis "Iteration construct for Common Lisp")
+ (description "@code{iterate} is an iteration construct for Common Lisp.
+It is similar to the @code{CL:LOOP} macro, with these distinguishing marks:
+
+@itemize
+@item it is extensible,
+@item it helps editors like Emacs indent iterate forms by having a more
+ lisp-like syntax, and
+@item it isn't part of the ANSI standard for Common Lisp.
+@end itemize\n")
+ (license license:expat)))
--
2.12.2
next prev parent reply other threads:[~2017-05-29 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 16:53 bug#27132: [PATCH 0/6] Add uglify-js Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 2/6] gnu: Add sbcl-parse-js Ricardo Wurmus
2017-06-01 12:00 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 3/6] gnu: Add sbcl-parse-number Ricardo Wurmus
2017-06-01 12:01 ` Ludovic Courtès
2017-05-29 17:21 ` Ricardo Wurmus [this message]
2017-06-01 12:01 ` bug#27132: [PATCH 4/6] gnu: Add sbcl-iterate Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 5/6] gnu: Add sbcl-cl-uglify-js Ricardo Wurmus
2017-06-01 12:02 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 6/6] gnu: Add uglify-js Ricardo Wurmus
2017-06-01 12:03 ` Ludovic Courtès
2017-06-01 21:33 ` Ricardo Wurmus
2017-06-02 19:00 ` Arun Isaac
2017-06-01 12:00 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ludovic Courtès
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=20170529172131.20954-4-rekado@elephly.net \
--to=rekado@elephly.net \
--cc=27132@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).