Hi,
As some extra info:
`guix shell` by default does what `guix environment --ad-hoc` did.
And `guix shell --development` is what `guix environment` was.
They are equivalent, but the flags might be confusing at the beginning!
Happy hacking!
Ekaitz
[ElenQ Technology](https://elenq.tech)
Ethical I
Hello : )
Thank you both! I did not know that. I previously mistakenly thought
"environment = shell", but did not know, that I would have to add `-D` or
`--development` to actually make an equivalent call. So `guix shell`, I guess,
is more nuanced then, than `guix environment`.
Anyway, that
Zelphir Kaltstahl writes:
> I am messing around again with updating a package and according to my
> own guide from previous adventures, I have to run the following
> command to generate the `pre-inst-env` script, in the root directory
> of the guix sources:
>
>
> guix environment guix -- ./
Hi,
Isn't `guix environment guix` equivalent to `guix shell -D guix`?
I think you are missing a -D there so it's adding a shell with guix and not
with its development dependencies.
Hope that helps,
Ekaitz
[ElenQ Technology](https://elenq.tech)
Ethical Innovation
--- Original Message ---
That's because you're not using guix shell properly.
guix shell guix
Creates a shell where guix *itself* is available
guix shell -D guix
Creates a shell where guix *dependencies* are available. That's what you need
to use.
The manual provides more information on how to build Guix from the sou
On 7/8/22 23:57, Zelphir Kaltstahl wrote:
Hello Guix developers!
I am messing around again with updating a package and according to my own
guide from previous adventures, I have to run the following command to
generate the `pre-inst-env` script, in the root directory of the guix sources:
~~
Hello Guix developers!
I am messing around again with updating a package and according to my own guide
from previous adventures, I have to run the following command to generate the
`pre-inst-env` script, in the root directory of the guix sources:
guix environment guix -- ./bootstrap
