From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Programmer <programmer@verisimilitudes.net>
Cc: guix-devel@gnu.org
Subject: Re: Lisp libraries: Other variants? (CCL, CLisp, etc.)
Date: Mon, 05 Nov 2018 22:03:35 +0100 [thread overview]
Message-ID: <87o9b3b5js.fsf@ambrevar.xyz> (raw)
In-Reply-To: <36sgl312.fsf@server.domain.com>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Hi again!
Thanks for your proposal, it brings up some interesting ideas.
Have you looked at lisp-utils.scm? I think it incorporates some of your ideas
already. It could perhaps be generalized following your ideas so that it works
for all Lisps out of the box.
Question: Are .fasl files compatible across Common Lisp implementations? If
not, then what's your suggestion?
I have a few more questions:
> The idea is simpler packaging, through a system called PACKAGER, which would provide a very
> high-level and exhaustive declaration of an entire Common Lisp package or collection of packages
By "system", do you mean a _build system_ or something else?
> This location could default to "~/.common-lisp/" and be controlled through an environmental
> variable, with a name such as GUIX_COMMON_LISP_HOME.
We want to install libraries in the store. Why do you suggest we put it in the
user's home?
> As the files actually loaded by this system
> proposed would be generated as needed and for the system, that eliminates this.
Sorry, I don't understand how your proposal would eliminate the POSIX-assumption
issue. Can you provide an example?
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-05 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 1:35 Lisp libraries: Other variants? (CCL, CLisp, etc.) Programmer
2018-11-05 21:03 ` Pierre Neidhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2018-10-20 10:10 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
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=87o9b3b5js.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=programmer@verisimilitudes.net \
/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).