From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
52727@debbugs.gnu.org
Subject: bug#52727: When logged as user, GUILE_LOAD_COMPILED_PATH points to the system cache instead of the user cache
Date: Wed, 22 Dec 2021 12:03:42 +0100 [thread overview]
Message-ID: <c73c839f828f4761c3e6c1dc5bb3cc5a1e5215f6.camel@ist.tugraz.at> (raw)
In-Reply-To: <8f566ce905caa66d70c201bc7cfbc07d52949b29.camel@telenet.be>
Am Mittwoch, dem 22.12.2021 um 11:32 +0100 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op wo 22-12-2021 om 08:57 [+0100]:
> > No. The Guix command as built by `guix pull' sets its own load path,
> > but respects system paths too. You can check by spawning a REPL:
> > [...]
>
> But are there any good reasons to respect $GUILE_LOAD{,_COMPILE}_PATH
> at all? Usually, we use wrap-program etc. to set load paths (guile,
> python, PATH or otherwise). Maybe guile-launcher can be modified to set
> the load path instead of appending to it?
IIUC the guix command does not particularly need to provide support for
multiple profiles, so we could isolate it. After all, extensions ought
to be installed in the user's (single) current-guix profile, no?
(Disregarding the use of guix environment/guix shell, of course.) Or
more accurately, GUIX_EXTENSIONS_PATH serves as a different escape
hatch.
prev parent reply other threads:[~2021-12-22 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 0:16 bug#52727: When logged as user, GUILE_LOAD_COMPILED_PATH points to the system cache instead of the user cache Denis 'GNUtoo' Carikli
2021-12-22 7:57 ` Liliana Marie Prikler
2021-12-22 10:29 ` Maxime Devos
2021-12-23 7:31 ` Denis 'GNUtoo' Carikli
2021-12-23 8:22 ` Liliana Marie Prikler
2021-12-22 10:32 ` Maxime Devos
2021-12-22 11:03 ` Liliana Marie Prikler [this message]
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=c73c839f828f4761c3e6c1dc5bb3cc5a1e5215f6.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=52727@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.org \
--cc=maximedevos@telenet.be \
/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.