@civodul To me it’s important that the guix environment stays around. I have quite a bit of infrastructure in shell-scripts that relies on it.
This is a useful improvement. --ad-hoc bugged me quite some times. I also like the idea of caching
@civodul It would be cool to have both environment and shell because they serve different (but similar) goals.
I really like this one, very handy!
@civodul I always envisioned that 'guix environment' could be used without arguments and it would read a manifest file that followed a naming convention (say, guix.scm) and it would be a universal replacement for `npm install`, `bundle install`, `pip install`, etc. it would cache, just like `guix shell` is now doing, though guix shell's cache seems scoped to the current user, rather than the current project, which doesn't feel right to me.
@dthompson I know! I’d have kept the name, but wisdom says we cannot “inverse” semantics and keep the same name, we’d just create a big mess.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!