From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 68498@debbugs.gnu.org
Subject: [bug#68498] [PATCH] guix-install.sh: Make Guix modules available too.
Date: Thu, 25 Jan 2024 09:00:25 +0100 [thread overview]
Message-ID: <87wmrxc06e.fsf@gnu.org> (raw)
In-Reply-To: <877cjys762.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 24 Jan 2024 23:22:45 +0100")
Ludovic Courtès writes:
Hi,
> Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
>
>> * etc/guix-install.sh (GUILE_LOAD_PATH): Prepend directory to current Guix
>> modules.
>> (GUILE_LOAD_COMPILED_PATH): Likewise to compiled modules.
[..]
>> +# Make Guix modules available
>> +export GUILE_LOAD_PATH="$_GUIX_PROFILE/share/guile/site/3.0${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
>> +export GUILE_LOAD_COMPILED_PATH="$_GUIX_PROFILE/lib/guile/3.0/site-ccache${GUILE_LOAD_COMPILED_PATH:+:}$GUILE_LOAD_COMPILED_PATH"
>
> My inclination would be to let people just use ‘guix repl’, but maybe
> that’s not satisfactory or convenient? WDYT?
The intention is to have the foreign distro experience resemble Guix
System more, esp. for newbee users. If you have a code base that uses
Guix modules and comes with a guix.scm, running "guix shell" doesn't
work for them. Unless, maybe, you add "guix" to the package's
native-inputs -- yuck.
They'd have to probably do something guix time-machine --channel=xxx to
get access to guix modules. That, or source a script that set the
environment variables, which is what we let them do currently. I was
guessing "everyone" is probably fighting with this, so finally decided
to upstream it :)
If there's a better/easier solution for this, I'm all ears!
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
next prev parent reply other threads:[~2024-01-25 8:01 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 [this message]
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
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=87wmrxc06e.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=68498@debbugs.gnu.org \
--cc=ludo@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 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.