Hi!
Sarah Morgensen skribis:
> However, an actual `guix env' could do a lot more! Like you allude to, being
> able to essentially save the options of a `guix environment' invocation would
> be great:
>
> $ guix env --edit @test
> $ guix env @test -- pytest
Perhaps not as convenient
Hi,
On Sun, 12 Sep 2021 at 12:33, Sarah Morgensen wrote:
> Ryan Prior writes:
>> I've been thinking lately it would be convenient to create certain uniquely
>> named execution environments on my machine. For example, I might have one
>> set up with dependencies for my Python webapp &
Ryan Prior writes:
> Hey Guix.
>
> I've been thinking lately it would be convenient to create certain uniquely
> named execution environments on my machine. For example, I might have one
> set up with dependencies for my Python webapp & environment variables set to
> autoconnect to a Postgres
Hi Ryan:
> I might write a wrapper in some scripting language that sets up this kind of
> system. Would anybody else be interested in using such a thing? Would it make
> sense to integrate this capability into Guix itself?
I've been using something like that with shell scripts and manifests. I
Hey Guix.
I've been thinking lately it would be convenient to create certain uniquely
named execution environments on my machine. For example, I might have one set
up with dependencies for my Python webapp & environment variables set to
autoconnect to a Postgres server. I might have another
