all messages for Guix-related lists mirrored at yhetil.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: Mon, 09 Aug 2021 20:30:41 +0000	[thread overview]
Message-ID: <87v94ejr7y.fsf@kitej> (raw)
In-Reply-To: <U4bfmgGzxirkNolhMn7ji23Akkw9Igu8yXpjAY8BJXtNZazqaSwjGxqZh35FRaVchK6lJgXCYYBIu4vI_pmLG_RJMWbyJaoXT_owZoW9Mno=@protonmail.com>

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

Charles via Guix-patches via <guix-patches@gnu.org> skribis:

> I'm pretty sure this is correct and I have confired on the irc. Open to conversation though.

Hi,

Instead of propagating the dependencies, we use configuration files
indicating to ASDF where to find the sources and compiled files of the
dependencies in the store.

These configuration files are in "$GUIX_PROFILE/etc/common-lisp"
or "$GUIX_ENVIRONMENT/etc/common-lisp".

Do you have a use case where the Common Lisp implementation fails to
find dependencies?
If yes, could you give an example?

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

  reply	other threads:[~2021-08-09 20:31 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 [this message]
2021-08-09 20:58   ` Charles via Guix-patches via
2021-08-10  8:10     ` Guillaume Le Vaillant
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v94ejr7y.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 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.