all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Charles via Guix-patches via <guix-patches@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 49965@debbugs.gnu.org
Subject: [bug#49965] Correct Input type for Common Lisp packages
Date: Mon, 09 Aug 2021 20:58:59 +0000	[thread overview]
Message-ID: <aBUpD-9LhVtwdB30I6HE7kqlsdXDe226Sf388Usw2SH7rPVdtFbLHg5k0NzV-j03aMhK0obth17eXpa8AWUUP32LUwpRip8QD7-NcYHSxrY=@protonmail.com> (raw)
In-Reply-To: <87v94ejr7y.fsf@kitej>

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.

What advantage is there to avoiding propagated-inputs?

Also whatever the solution is should probably been in the manual, or better yet automatically loaded by Common Lisp in a system level init file.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, August 9th, 2021 at 3:30 PM, Guillaume Le Vaillant <glv@posteo.net> wrote:

> 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?




  reply	other threads:[~2021-08-09 21:00 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 [this message]
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='aBUpD-9LhVtwdB30I6HE7kqlsdXDe226Sf388Usw2SH7rPVdtFbLHg5k0NzV-j03aMhK0obth17eXpa8AWUUP32LUwpRip8QD7-NcYHSxrY=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=49965@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    --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.