From: Eric Bavier <bavier@member.fsf.org>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: gnu: Add CLISP.
Date: Thu, 12 Feb 2015 21:20:52 -0600 [thread overview]
Message-ID: <20150212212052.687467f1@PocketWee> (raw)
In-Reply-To: <87lhk2eloq.fsf@taylan.uni.cx>
On Fri, 13 Feb 2015 00:48:05 +0100
taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer) wrote:
> From 6201470b3e6c2410be7f38d8cc1cc99c3b13f0da Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
> <taylanbayirli@gmail.com>
> Date: Thu, 12 Feb 2015 22:19:52 +0100
> Subject: [PATCH] gnu: Add CLISP.
>
> * gnu/packages/lisp.scm (clisp): New variable.
[...]
> + (arguments
> + '(#:phases
> + (alist-cons-after
> + 'unpack 'post-unpack
Could you use a more descriptive phase name? E.g. "patch-sh-and-pwd"?
> + (alist-cons-before
> + 'build 'pre-build
Ditto. Several other packages use "chdir" or "chdir-to-source"
> + ;; Parallel builds seem to fail.
> + #:parallel-build? #f))
If you know more specifically why parallel builds fail, could you
comment on that? Race conditions, or not using $(MAKE), etc?
> + (home-page "http://www.clisp.org/")
> + (synopsis "A feature-rich Common Lisp implementation")
Do not begin with "A"; `guix lint` will complain about that. Perhaps
just "Common Lisp implementation".
> + (description "GNU CLISP is an implementation of ANSI Common
> Lisp, with +many extensions. It includes an interpreter, compiler,
^
"+many" -> "many"
> debugger, CLOS, MOP, +an FFI, i18n, POSIX and Perl regular
^
"+an" -> "an"
> expressions, a socket interface, fast +bignums, arbitrary precision
^
"+bignums" -> "bignums"
> floats, and more. An X11 interface is available +through CLX, Garnet
^
"+through" -> "through"
> and CLUE/CLIO. Command line editing is provided by +readline.")
^
"+readline" -> "readline"
Copy and paste + wrapping errors? ;)
> + ;; Website says gpl2+, COPYRIGHT file says gpl2; actual source
> files have
> + ;; a lot of gpl3+. (Also some parts are under non-copyleft
> licenses, such
> + ;; as CLX by Texas Instruments.)
> + (license (list license:gpl2 license:gpl2+ license:gpl3+))))
I think in this case the gpl3+ might "win out", but I'll let others
comment on that.
Thanks!
`~Eric
next prev parent reply other threads:[~2015-02-13 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 23:48 gnu: Add CLISP Taylan Ulrich Bayırlı/Kammer
2015-02-13 3:20 ` Eric Bavier [this message]
2015-02-13 7:35 ` Mark H Weaver
2015-02-13 10:39 ` Taylan Ulrich Bayırlı/Kammer
2015-02-13 13:26 ` Eric Bavier
2015-02-13 10:33 ` Taylan Ulrich Bayırlı/Kammer
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=20150212212052.687467f1@PocketWee \
--to=bavier@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@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).