unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Charles <charles.b.jackson@protonmail.com>
Cc: 49965@debbugs.gnu.org
Subject: [bug#49965] Correct Input type for Common Lisp packages
Date: Tue, 10 Aug 2021 08:10:19 +0000	[thread overview]
Message-ID: <871r71pvo4.fsf@kitej> (raw)
In-Reply-To: <aBUpD-9LhVtwdB30I6HE7kqlsdXDe226Sf388Usw2SH7rPVdtFbLHg5k0NzV-j03aMhK0obth17eXpa8AWUUP32LUwpRip8QD7-NcYHSxrY=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

Charles <charles.b.jackson@protonmail.com> skribis:

> I didn't know I about theses conf files, and after seeing them, I'm
> not sure how to use them. Not to mention: I don't have
> a $GUIX_PROFILE/etc/common-lisp.
>
> Up to now I have been using a config like the following:
>
> (require :asdf)
> (uiop:appendf
>  asdf:*central-registry*
>  (list (uiop:getcwd))
>  (directory
>   (concatenate
>    'string
>    (or (uiop:getenv "GUIX_ENVIRONMENT")
>        "~/.guix-profile")
>    "/share/common-lisp/"
>    (case uiop:*implementation-type*
>      ((:sbcl) "sbcl")
>      ((:ecl) "ecl")
>      (otherwise "source"))
>    "/*")))
>
> which I find quite readable, although probably not perfect.

The "$GUIX_PROFILE/etc/common-lisp" directory will only be there if you
have at least one Common Lisp package installed in the profile.

ASDF should be able to find sources and compiled libraries by itself
(it's using XDG_CONFIG_DIRS and XDG_DATA_DIRS to find the
configuration files created by asdf-build-system and populate the
source registry and the output translations).
I suspect that your custom 'asdf:*central-registry*' is superseding the
default configuration, causing ASDF to ignore the
'etc/common-lisp/source-registry.conf.d/*' files.
Could you try without it to see if it works?


> What advantage is there to avoiding propagated-inputs?

I think it's the philosophy of GNU Guix to use references to the store
by default, and use input propagation only when it's the only way to get
things to work. This way the profiles are less cluttered.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-08-10  8:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 17:19 [bug#49965] Correct Input type for Common Lisp packages Charles via Guix-patches via
2021-08-09 20:30 ` Guillaume Le Vaillant
2021-08-09 20:58   ` Charles via Guix-patches via
2021-08-10  8:10     ` Guillaume Le Vaillant [this message]
2021-08-11 23:39       ` Charles via Guix-patches via
2021-08-12  8:51         ` Guillaume Le Vaillant
2021-08-12 13:47           ` Charles via Guix-patches via
2021-08-13  7:33             ` Guillaume Le Vaillant
2021-08-14  0:38               ` Charles via Guix-patches via
2021-08-14  9:48                 ` bug#49965: " Guillaume Le Vaillant

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=871r71pvo4.fsf@kitej \
    --to=glv@posteo.net \
    --cc=49965@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    /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).