GNU bug report logs - #46291
[PATCH] environment: Allow starting from existing profile

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 46291 in the body.
You can then email your comments to 46291 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lars-Dominik Braun <lars <at> 6xq.net>
To: guix-patches <at> gnu.org
Subject: [PATCH] environment: Allow starting from existing profile
Date: Thu, 4 Feb 2021 11:13:20 +0100

[Message part 1 (text/plain, inline)]

Hi everyone,

the attched patch allows starting a `guix environment` from an existing
profile. Our use-case is this: We have profiles, created by

	guix package -p /path -i …

because we need to parse desktop files in /path/share/applications. Also
this does the heavy-lifting (substitutes/building/grafting) upfront once
and not when starting an environment. Then we start an application from
this profile using

	guix environment -C […] -p /path -- jupyterlab […]

This is much faster (10x) for large profiles (i.e. JupyterLab) than

	guix environment -C […] -m manifest.scm -- jupyterlab […]

and makes sure the environment is exactly the same as

	source /path/etc/profile

I think there have been many discussions about how `guix environment`
should work and this is certainly not the silver bullet, but it’s a huge
improvement for us with very limited code changes required.

Cheers,
Lars

[0001-environment-Allow-starting-from-existing-profile.patch (text/x-diff, attachment)]

Message #10 received at 46291-done <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> outlook.com>
To: Lars-Dominik Braun <lars <at> 6xq.net>
Cc: 46291-done <at> debbugs.gnu.org
Subject: Re: [bug#46291] [PATCH] environment: Allow starting from existing
 profile
Date: Thu, 11 Feb 2021 18:01:31 +0800

Lars-Dominik Braun <lars <at> 6xq.net> writes:

> Hi everyone,
>
> the attched patch allows starting a `guix environment` from an existing
> profile. Our use-case is this: We have profiles, created by
>
> 	guix package -p /path -i &
>
> because we need to parse desktop files in /path/share/applications. Also
> this does the heavy-lifting (substitutes/building/grafting) upfront once
> and not when starting an environment. Then we start an application from
> this profile using
>
> 	guix environment -C [&] -p /path -- jupyterlab [&]
>
> This is much faster (10x) for large profiles (i.e. JupyterLab) than
>
> 	guix environment -C [&] -m manifest.scm -- jupyterlab [&]
>
> and makes sure the environment is exactly the same as
>
> 	source /path/etc/profile
>
> I think there have been many discussions about how `guix environment`
> should work and this is certainly not the silver bullet, but it.s a huge
> improvement for us with very limited code changes required.

Look excellent to me, pushed, thank you!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.