From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 56334@debbugs.gnu.org
Subject: bug#56334: Should asdf-build-system/sbcl use load-system instead of compile-system?
Date: Sun, 03 Jul 2022 10:19:53 +0000 [thread overview]
Message-ID: <87tu7ypk5s.fsf@kitej> (raw)
In-Reply-To: <875ykfkedc.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Robert Goldman from ASDF found out why the "COMPONENT not found" issue happens:
>
> https://gitlab.common-lisp.net/asdf/asdf/-/issues/119#note_9808
>
> So either we fix most of the Prove-depending libraries, or we just do
> what's expected from every one, that is, add the directory to the ASDF
> registries.
>
> The latter is much easier of course...
As adding the build directory to ASDF's registry is easier and also
simplifies asdf-build-system, would should do that. And we could still
open issues upstream for libraries that are starting their test suites
in a wrong way.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-07-03 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 10:16 bug#56334: Should asdf-build-system/sbcl use load-system instead of compile-system? Pierre Neidhardt
2022-07-01 11:13 ` Guillaume Le Vaillant
2022-07-01 11:45 ` Pierre Neidhardt
2022-07-01 12:22 ` Guillaume Le Vaillant
2022-07-01 14:46 ` Pierre Neidhardt
2022-07-01 16:40 ` Guillaume Le Vaillant
2022-07-01 17:07 ` Pierre Neidhardt
2022-07-02 10:17 ` Pierre Neidhardt
2022-07-03 10:19 ` Guillaume Le Vaillant [this message]
2022-07-04 15:18 ` Pierre Neidhardt
2022-07-04 19:57 ` Pierre Neidhardt
2022-07-05 8:56 ` Pierre Neidhardt
2022-07-17 16:19 ` Pierre Neidhardt
2022-08-03 14:49 ` Guillaume Le Vaillant
2022-08-04 14:01 ` Pierre Neidhardt
2022-07-01 14:30 ` Liliana Marie Prikler
2022-07-01 14:43 ` 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=87tu7ypk5s.fsf@kitej \
--to=glv@posteo.net \
--cc=56334@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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).