all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 68498@debbugs.gnu.org, Janneke Nieuwenhuizen <janneke@gnu.org>
Subject: [bug#68498] [PATCH] guix-install.sh: Make Guix modules available too.
Date: Tue, 02 Apr 2024 17:26:25 +0200	[thread overview]
Message-ID: <87il0z4wgu.fsf@gnu.org> (raw)
In-Reply-To: <87plw2dh0w.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 09 Mar 2024 20:14:55 -0500")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>>> 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.
>
> I don't quite like the status quo where Guix System is different from
> Guix on a foreign distribution for dubious reasons.  Either we expose
> the Guix modules as part of the guix-install.sh or perhaps we can avoid
> exposing them on Guix System, for consistency.
>
> What do you think?

Sorry for the delay.  It’s probably not that big a deal so if you think
this improves user experience, go for it; I don’t want to block this
change.  Worst that can happen is we change our mind and revert it,
that’s OK.

Ludo’.




  reply	other threads:[~2024-04-02 15:27 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
2024-03-10  1:14           ` Maxim Cournoyer
2024-04-02 15:26             ` Ludovic Courtès [this message]
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

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

  git send-email \
    --in-reply-to=87il0z4wgu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=68498@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=maxim.cournoyer@gmail.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.