From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Problems with McCLIM (Common Lisp)
Date: Fri, 11 Sep 2020 16:40:41 +0200 [thread overview]
Message-ID: <87o8mc74wm.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87blicgzvc.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
> To try and side-step the aforementioned issues with Guix's bundling
> code, I tried using the compile-bundle-op operation and a few others,
> and none of them worked with package-inferred systems. I believe I did
> some research and found that there was some esoteric reason these
> operations didn't work with package-inferred systems. I would be
> delighted if they did.
I had a discussion with upstream ASDF: if I recall correctly,
compile-bundle-op is not (easily) compatible with package-inferred
style.
Anyways, we should not use compile-bundle-op: this would solve so many
issues, including this one.
> We do need to overhaul how we package Common Lisp software in general.
> Regardless of whether the functionality we're discussing works, I think
> we have many more "standard" options for laying out packages and fasls
> on disk. We might want to consider looking closely at what Quicklisp
> does and see if we can't map that onto the store.
Quicklisp does not compile the Lisp files: it's roughly equivalent to
our cl-* packages. So there is not much to learn from Quicklisp because
what we want here is provide pre-compiled packages.
And thanks for your numerous contributions! :)
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-09-11 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 2:43 Problems with McCLIM (Common Lisp) Ricardo Wurmus
2020-08-13 7:16 ` Pierre Neidhardt
2020-08-13 9:08 ` Guillaume Le Vaillant
2020-09-04 16:37 ` Ricardo Wurmus
2020-09-05 6:57 ` Pierre Neidhardt
2020-09-05 7:20 ` Ricardo Wurmus
2020-09-05 9:49 ` Guillaume Le Vaillant
2020-09-05 17:52 ` Konrad Hinsen
2020-09-06 7:07 ` Pierre Neidhardt
2020-09-11 14:19 ` Katherine Cox-Buday
2020-09-11 14:40 ` Pierre Neidhardt [this message]
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=87o8mc74wm.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cox.katherine.e@gmail.com \
--cc=help-guix@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.