all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Simon Tournier" <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: What's the difference between a shell environment and a profile?
Date: Mon, 11 Dec 2023 11:47:12 +0100	[thread overview]
Message-ID: <m1h6kpf233.fsf@fastmail.net> (raw)
In-Reply-To: <87r0jv63lk.fsf@gnu.org>

Hi Simon and Ludo,

>> It does not differ.  What differs is that “guix shell” raises nothing
>> for the collision – maybe “guix shell” does not check the collision, I
>> do not remember – when “guix package” raises an error for the same
>> collision.
>
> Indeed, ‘guix shell’ does not check collisions, for “historical
> reasons”.  Perhaps something worth fixing at some point:
>
>   https://issues.guix.gnu.org/54350

Thanks for pointing out this behavior, which I find surprising but
understandable for the use case of development environments (although I
didn't expect collisions to be so frequent even in that context).

The problem I have now is how to update my recommendations for
computational scientists, which can be summarized as "run all research
computation in "guix shell" (see
e.g. https://10years.guix.gnu.org/program/#guix-as-a-tool-for-computational-science). As
I just found out, I am recommending people to switch off an important
level of error checking.

I'll think about this a bit and then perhaps comment on the old issue
thread!

Cheers,
  Konrad.


      reply	other threads:[~2023-12-11 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 16:24 What's the difference between a shell environment and a profile? Konrad Hinsen
2023-12-08 17:35 ` Simon Tournier
2023-12-09 11:02   ` Ludovic Courtès
2023-12-11 10:47     ` Konrad Hinsen [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

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

  git send-email \
    --in-reply-to=m1h6kpf233.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.