From: "Ludovic Courtès" <ludo@gnu.org>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: 68498@debbugs.gnu.org
Subject: [bug#68498] [PATCH] guix-install.sh: Make Guix modules available too.
Date: Mon, 29 Jan 2024 17:05:44 +0100 [thread overview]
Message-ID: <87h6iwnmzr.fsf@gnu.org> (raw)
In-Reply-To: <878r48z76a.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Mon, 29 Jan 2024 12:54:21 +0100")
Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
>> Packages that extend Guix functionality, like Cuirass and hpcguix-web,
>> have ‘guix’ in their inputs. That’s fine: they use just the core (guix …)
>> modules to interact with the store etc.
>>
>> Is that what the kind of use case you had in mind?
>
> Yes. I always believed this was a big no-no, but adding guix to the
> packages' inputs in guix.scm would also work.
Yes, and it’s even unavoidable for software that depends on (guix …)
modules.
> I'm still somewhat puzzled about why setting GUILE_LOAD[_COMPILED]_PATH
> would be a bad idea, but unless someone else decides to chimes some time
> soon in I guess we can close this bug.
It’s not too bad, but (1) it could break the user’s setup (for instance
if they’ve installed some incompatible Guile versions via the host
distro and all of a sudden Guile 3.0.9 modules show up in the search
path), and (2) one could just as well consider special-casing ‘CPATH’ or
‘GUIX_PYTHONPATH’.
So I think we can close, but again, if I misunderstood how the status
quo is a hindrance, I’m open to this change or any other solution.
Ludo’.
next prev parent reply other threads:[~2024-01-29 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:27 [bug#68498] [PATCH] guix-install.sh: Make Guix modules available too Janneke Nieuwenhuizen
2024-01-24 22:22 ` Ludovic Courtès
2024-01-25 8:00 ` Janneke Nieuwenhuizen
2024-01-29 11:22 ` Ludovic Courtès
2024-01-29 11:54 ` Janneke Nieuwenhuizen
2024-01-29 16:05 ` Ludovic Courtès [this message]
2024-03-10 1:14 ` Maxim Cournoyer
2024-04-02 15:26 ` Ludovic Courtès
2024-04-07 14:37 ` bug#68498: " Janneke Nieuwenhuizen
2024-04-18 19:03 ` [bug#68498] " Janneke Nieuwenhuizen
2024-04-19 11:40 ` Maxim Cournoyer
2024-04-19 14:58 ` Janneke Nieuwenhuizen
2024-04-20 3:36 ` Liam Hupfer via Guix-patches via
2024-04-20 21:28 ` Maxim Cournoyer
2024-04-21 2:07 ` Liam Hupfer via Guix-patches via
2024-04-21 6:15 ` Janneke Nieuwenhuizen
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=87h6iwnmzr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=68498@debbugs.gnu.org \
--cc=janneke@gnu.org \
/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).