From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 45017@debbugs.gnu.org
Subject: bug#45017: asdf-build-system packages have priority over user ones
Date: Fri, 04 Dec 2020 10:12:06 +0100 [thread overview]
Message-ID: <871rg6szo9.fsf@yamatai> (raw)
In-Reply-To: <87k0tyuf6y.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Thanks for taking a shot at this, looks great!
>
> I'll test later, but for now one question: we patch sbcl to use our
> cl-asdf, but what about the other compilers? Seems to me that the other
> compilers are going to have the same problem, aren't they?
SBCL and ECL are patched to use our cl-asdf because it is necessary to
build the sbcl-* and ecl-* packages. Also patching ABCL, CCL, and Clisp
sounds like a good idea. At least all the compilers would use the same
version of ASDF, and hopefully behave in the same way when looking for
configuration files.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-04 9:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 9:42 bug#45017: asdf-build-system packages have priority over user ones Pierre Neidhardt
2020-12-03 12:04 ` Guillaume Le Vaillant
2020-12-03 12:40 ` Pierre Neidhardt
2020-12-03 14:29 ` Guillaume Le Vaillant
2020-12-04 8:51 ` Pierre Neidhardt
2020-12-04 9:12 ` Guillaume Le Vaillant [this message]
2020-12-04 12:46 ` Pierre Neidhardt
2020-12-04 13:53 ` Guillaume Le Vaillant
2020-12-04 17:30 ` Guillaume Le Vaillant
2020-12-05 8:18 ` Pierre Neidhardt
2020-12-05 9:42 ` Guillaume Le Vaillant
2020-12-05 9:17 ` Pierre Neidhardt
2020-12-05 10:03 ` Guillaume Le Vaillant
2020-12-05 10:52 ` Guillaume Le Vaillant
2020-12-05 14:42 ` Pierre Neidhardt
2020-12-05 15:17 ` Guillaume Le Vaillant
2020-12-05 15:19 ` 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=871rg6szo9.fsf@yamatai \
--to=glv@posteo.net \
--cc=45017@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).