From: Tim Lee <progscriptclone@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: cl-asdf: where is its asd file?
Date: Thu, 25 Feb 2021 04:33:35 +0800 [thread overview]
Message-ID: <3147176a-0a19-d50e-cca9-3a2439c7ed04@gmail.com> (raw)
In-Reply-To: <87pn0pe85x.fsf@yamatai>
> So far the cl-asdf package in Guix is only used to update the ASDF
> bundled in the sbcl, ecl, ccl and clisp packages, so that they all use
> the same version of ASDF.
>
> Instead of using 'require', it should work if you just load the file:
>
> --8<---------------cut here---------------start------------->8---
> (load (merge-pathnames ".guix-profile/share/common-lisp/source/asdf/asdf.lisp"
> (user-homedir-pathname)))
> --8<---------------cut here---------------end--------------->8---
>
> Or you could use the sbcl from Guix instead of the Ubuntu one.
Okay. Thank you for the explanation. I just found it a bit strange that
a cl-* package does not contain an asd file, especially when one is
already provided by the upstream
(https://gitlab.common-lisp.net/asdf/asdf/). Interesting that the ASDF
package itself has no asd file!
Perhaps the maintainer(s) should consider including an asd file to avoid
surprises like this.
next prev parent reply other threads:[~2021-02-24 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:10 cl-asdf: where is its asd file? Tim Lee
2021-02-24 16:34 ` Guillaume Le Vaillant
2021-02-24 20:33 ` Tim Lee [this message]
2021-02-25 9:42 ` Pierre Neidhardt
2021-02-26 15:15 ` Tim Lee
2021-02-26 15:51 ` Pierre Neidhardt
2021-02-27 14:09 ` Tim Lee
2021-02-27 14:23 ` 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=3147176a-0a19-d50e-cca9-3a2439c7ed04@gmail.com \
--to=progscriptclone@gmail.com \
--cc=glv@posteo.net \
--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.
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).