Hi,
Jacob Hrbek skribis:
> Doesn't seem to work on `busybox sh` for me (I am not aware of better way to
> replicate POSIX environment on GNU Guix):
Note that you’re running /usr/bin/env, which has nothing to do with
Busybox.
> kreyren@leonid ~$ guix shell busybox -- busybox sh
> ...
> ~ $ cat
Doesn't seem to work on `busybox sh` for me (I am not aware of better way to
replicate POSIX environment on GNU Guix):
kreyren@leonid ~$ guix shell busybox -- busybox sh
...
~ $ cat test.sh
#!/usr/bin/env -S guix shell --
(use-modules
(guix channels))
(list (channel
(name 'guix
Hey Jacob,
On Tue, Nov 09 2021, Jacob Hrbek wrote:
For now I use “#!/usr/bin/env -S guix shell --”, which works
well enough for me. How does that sound? -- l...@gnu.org
Not a solution as (AFIAK) POSIX only accepts one argument.
That's the point of the -S. It passes the entire rest of the li
> For now I use “#!/usr/bin/env -S guix shell --”, which works well enough for
> me. How does that sound? -- l...@gnu.org
Not a solution as (AFIAK) POSIX only accepts one argument.
-- Jacob "Kreyren" Hrbek
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, Novemb
Hi,
Jacob Hrbek skribis:
> I am unable to define a guix shell file with shebang to decrease the
> complexity needed in the repository managing (so
> that i can just do ./path/to/guix.scm for guix to invoke `guix shell -f
> ./path/to/guix.scm` instead of having to
> sanitize the runtime) as the
I am unable to define a guix shell file with shebang to decrease the complexity
needed in the repository managing (so that i can just do ./path/to/guix.scm for
guix to invoke `guix shell -f ./path/to/guix.scm` instead of having to sanitize
the runtime) as the issue is that POSIX shebang allows o
