From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 45017@debbugs.gnu.org
Subject: bug#45017: asdf-build-system packages have priority over user ones
Date: Thu, 03 Dec 2020 13:40:02 +0100 [thread overview]
Message-ID: <87360nm5b1.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87im9j2j06.fsf@yamatai>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
Oh, I had missed that! Good thing I asked you first then ;)
> --8<---------------cut here---------------start------------->8---
> (substitute* dst-asdf
> (("\\(xdg-config-pathname \\*source-registry-directory\\* direction\\)")
> "`(:source-registry
> (:include (xdg-config-home \"common-lisp/source-registry.conf.d/\"))
> ,@(loop
> for dir in (xdg-config-dirs
> \"common-lisp/source-registry.conf.d/\")
> collect `(:include ,dir))
> :inherit-configuration)")
> (("\\(xdg-config-pathname \\*output-translations-directory\\* direction\\)")
> "`(:output-translations
> (:include (xdg-config-home \"common-lisp/asdf-output-translations.conf.d/\"))
> ,@(loop
> for dir in (xdg-config-dirs
> \"common-lisp/asdf-output-translations.conf.d/\")
> collect `(:include ,dir))
> :inherit-configuration)")))
> --8<---------------cut here---------------end--------------->8---
Hmm, I don't think this would work when the user has no
~/.config/common-lisp/source-registry.conf.
Would it?
> Or maybe we could make a better patch not changing
> 'user-source-registry-directory', but adding a new
> 'guix-source-registry' between 'default-user-source-registry' and
> 'system-source-registry' in the list of registries (and likewise for
> output-translations).
> I think this way the systems in '$HOME/.config/...', '$HOME/.local/...'
> or '$HOME/common-lisp/...' will have priority on the ones in Guix
> profiles.
I like it!
Possible pitfall: if the user set *default-source-registries* in their
Lisp RC file (e.g. ~/.sbclrc) this will prevent ASDF from seeing this
new Guix source registry.
Alternately, we could simply move the patch from
user-source-registry-directory to system-source-registry-directory; same
for the output translation.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-12-03 12:41 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 [this message]
2020-12-03 14:29 ` Guillaume Le Vaillant
2020-12-04 8:51 ` Pierre Neidhardt
2020-12-04 9:12 ` Guillaume Le Vaillant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87360nm5b1.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=45017@debbugs.gnu.org \
--cc=glv@posteo.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 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.