Tobias Geerinckx-Rice <m...@tobias.gr> writes: > Christopher, > > Christopher Baines 写道： >> This seems to me like quite a big change, and I'd be interested >> in >> knowing what your motivation was [1]? > > It's not, really. It's equivalent to the impure /bin/sh that Guix > Systems already provide, but actually useful: ‘use > #!/usr/bin/env, not #!/bin/sh!’ was already a mantra when I wrote > my first shell script — and I'm not that young. > > There's no good argument for not being able to run the vast > majority of well-written scripts, out of the box, on Guix Systems.
If you are on Guix System and find that you need /usr/bin/env, you are already a "power user": you are venturing outside of what is provided by Guix alone. At that point you are expected to read the manual. Grepping for /usr/bin/env there will show you exactly what you need to do. Or perhaps you decide that it would be better to create a G-exp or package for the script. For running arbitrary scripts we have 'guix environment': perhaps it would make sense to add /usr/bin/env to `guix environment --container`?
signature.asc
Description: PGP signature
