bug#46291: closed ([PATCH] environment: Allow starting from existing profile)

[GNU bug Tracking System]

Your message dated Thu, 11 Feb 2021 18:01:31 +0800
with message-id 
<OSZP286MB066474D57DC1F59E3D191508A38C9@OSZP286MB0664.JPNP286.PROD.OUTLOOK.COM>
and subject line Re: [bug#46291] [PATCH] environment: Allow starting from 
existing profile
has caused the debbugs.gnu.org bug report #46291,
regarding [PATCH] environment: Allow starting from existing profile
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
46291: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46291
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] environment: Allow starting from existing profile Date: Thu, 4 Feb 2021 11:13:20 +0100

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
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [bug#46291] [PATCH] environment: Allow starting from existing profile
>
>
>
>
> Date: 
>
> Thu, 11 Feb 2021 18:01:31 +0800
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
>
>
>
>
> Lars-Dominik Braun <lars@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!
>
>
> --- End Message ---