[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Conda environments and reproducibility
From: |
Ludovic Courtès |
Subject: |
Re: Conda environments and reproducibility |
Date: |
Fri, 02 Dec 2022 11:52:11 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Hi Hugo,
Hugo Buddelmeijer <hugo@buddelmeijer.nl> skribis:
> By the way, it is quite hard to use conda in guix, primarily because "conda
> activate myenvironment" will try to set PS1 by calling a bash function
> called 'conda'. This bash function calls the 'conda' executable, which
> takes PS1, modifies it, and returns it to the bash function. The bash
> function subsequently sets PS1 (and makes a backup for deactivating the
> environment again). However, the conda executable is replaced by a bash
> script that calls conda_real. And bash scripts eat PS1 (because it is in
> non-interactive mode), so conda_real gets an empty PS1, fails to modify it,
> and then the bash function sets PS1 to nothing. I've got it working
> properly on my machine, but don't feel comfortable enough yet with Scheme /
> guix to provide a proper patch. The simplest might be to use another shell
> for the conda package (because I believe only bash eats PS1); not sure
> whether that is possible in guix. And I would rather make guix packages of
> everything and ditch conda altogether. But supporting conda properly would
> help more people transition.
Could you email it to bug-guix@gnu.org so we keep track of it?
Even if you cannot provide a patch, that will be a first step towards
fixing it.
Thanks,
Ludo’.