From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Andy Patterson <ajpatter@uwaterloo.ca>, Guix-devel <guix-devel@gnu.org>
Subject: Lisp libraries: Other variants? (CCL, CLisp, etc.)
Date: Sat, 20 Oct 2018 12:10:43 +0200 [thread overview]
Message-ID: <87k1mdormk.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hi guix,
Right now we have the following Lisp systems packaged in Guix:
- gcl
- ecl
- clisp
- sbcl
- ccl (Clozure)
- femtolisp
- lush2
(Am I missing any?)
For Common Lisp libraries, we have 3 ASDF-based build systems:
- asdf-build-system/sbcl: Build against SBCL (de facto choice?)
- asdf-build-system/ecl: Build against ECL
- asdf-build-system/source: Raw source.
Should we support more variants? For instance, CCL is fairly popular,
maybe it would be a good idea. If so, should we keep going with the
current method? That is to say, for Alexandria:
--8<---------------cut here---------------start------------->8---
(define-public cl-alexandria
(sbcl-package->cl-source-package sbcl-alexandria))
(define-public ecl-alexandria
(sbcl-package->ecl-package sbcl-alexandria))
; etc.
--8<---------------cut here---------------end--------------->8---
It can be a little verbose, maybe a function could help here, e.g.
--8<---------------cut here---------------start------------->8---
(define-lisp-package sbcl-alexandria cl ecl ccl)
--8<---------------cut here---------------end--------------->8---
But does it matter at all if we have the source build system? Can all
other implementations use cl-alexandria for instance?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-10-20 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 10:10 Pierre Neidhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-05 1:35 Lisp libraries: Other variants? (CCL, CLisp, etc.) Programmer
2018-11-05 21:03 ` Pierre Neidhardt
2018-11-09 6:45 Programmer
2018-11-09 11:02 ` Pierre Neidhardt
2018-11-09 20:17 ` Programmer
2018-11-10 10:02 ` Pierre Neidhardt
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=87k1mdormk.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=ajpatter@uwaterloo.ca \
--cc=guix-devel@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 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.