unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Charles via Guix-patches via <guix-patches@gnu.org>
To: zimon.toutoune@gmail.com, ludo@gnu.org
Cc: 54375@debbugs.gnu.org, maximedevos@telenet.be
Subject: [bug#54375] Mutable guix shell environments
Date: Tue, 15 Mar 2022 23:52:30 +0000	[thread overview]
Message-ID: <qvaBorHu9_h-bScZCkdB5pnXDKlNl4C6FmGVP_sMHD4YtVl2rG4W7kDaatQh4w4CU2hfoy9brbt_1C1iEptKo_G-XAhVEn-L81Wx-PEHUn0=@protonmail.com> (raw)
In-Reply-To: <CAJ3okZ0g5PcEmaMRJd6dubMaTXXNXGdY19LeZebzHRmEcOvxKg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Hello simon; thank you for your input.

> The "incremental style" is a quick and dirty approach for creating a computational environment

If profiles are used, it can be exported to a manifest.

> Guix is functional by design and we should not compromise on that.

I want to reiterate that I am not proposing anything less FP than profiles.

Nested shells do not fit my use case because a long running process started in shell "a" does not become aware of packages installed on shell "b".

> thus this "transient" profile should be manipulated via "guix shell" and not "guix package"

I chose "guix install" for my proposal because it already has the functionality of adding a new generation. I do not think it would be good to change the semantics of nested shells.

I failed to mention earlier that I like the name "--transient"

[-- Attachment #2: Type: text/html, Size: 1198 bytes --]

      reply	other threads:[~2022-03-15 23:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 18:21 [bug#54375] Mutable guix shell environments Charles via Guix-patches via
2022-03-13 19:51 ` Liliana Marie Prikler
2022-03-13 23:38   ` Charles via Guix-patches via
2022-03-14  5:19     ` Liliana Marie Prikler
2022-03-14  6:24       ` Charles via Guix-patches via
2022-03-14 17:43 ` Maxime Devos
2022-03-14 17:54 ` Maxime Devos
2022-03-14 19:41   ` Charles via Guix-patches via
2022-03-14 22:18   ` Ludovic Courtès
2022-03-15  9:49     ` zimoun
2022-03-15 23:52       ` Charles via Guix-patches via [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='qvaBorHu9_h-bScZCkdB5pnXDKlNl4C6FmGVP_sMHD4YtVl2rG4W7kDaatQh4w4CU2hfoy9brbt_1C1iEptKo_G-XAhVEn-L81Wx-PEHUn0=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=54375@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).