Re: guix environment --profile with --ad-hoc

[Lars-Dominik Braun]

Hi Pierre,

> Instead, I'd like the following behaviour:
> […]
hm, I feel that’s unnecessarly complex with lots of if’s and else’s. If
I could design the frontend from scratch, I’d have one command that does
profile/environment manipulation (because they’re essentially the same)
and one that can set them up for use. In that world you’d do

$ guix environment $(guix profile -m manifest.scm -i additional-package)

to get a temporary profile/environment and

# add a few packages
$ guix profile -p /path -m manifest.scm -i additional-package
/path
# remove one
$ guix profile -p /path -r additional-package
/path
# enter env
$ guix environment /path
$ ^D
# enter using container
$ guix environment -C --user=joeuser /path
$ ^D

to get a persistent environment and entering it without fiddling with -r
vs. -p vs. package options. In this case `guix environment` does not
know anything about packages and can only operate on existing profiles.

Maybe it’s possible to do profile inheritance like this too:

$ guix profile -p /new/profile -i /old/profile additional-package
/new/profile

which would be the union of /old/profile and {additional-package}.

Cheers,
Lars