You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2022. It is now read-only.
Describe the bug
When using buildFHSUserEnv in shell.nix, nix-shell properly sets up an FHS user environment with /usr/lib, /lib/... etc. When using lorri with the shame shell.nix, however, it is not properly setup.
It appears this is due to the architecture of direnv. buildFHSUserEnv depends on having a sub-shell in order to setup a chroot, but direnv just evaluates and updates environment variables.
Can you try using `lorri shell` instead? Does this work? It should run
the shell hook and then execute your normal user shell.
dmayle ***@***.***> writes:
It appears this is due to the architecture of direnv. buildFHSUserEnv depends on having a sub-shell in order to setup a chroot, but direnv just evaluates and updates environment variables.
Works fine with nix-shell, seems to evaluate with lorri shell but not at all with direnv. Notably, the chroot doesn't seem active when instantiated with lorri shell but does with nix-shell.
lorri --version
1.5.0
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When using buildFHSUserEnv in shell.nix, nix-shell properly sets up an FHS user environment with /usr/lib, /lib/... etc. When using lorri with the shame shell.nix, however, it is not properly setup.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The go library should build without errors
Metadata
lorri did not crash
Additional context
The text was updated successfully, but these errors were encountered: