Hadrien Mary

I was looking for a way to patch an env file recently (for usage inside a docker image but also inside a `setup-conda` GA) but couldn't find anything. I needed...

I actually started with `sed` but it was hard to make it work cross-platform and also because of often fancy chars in the version strings. We also use `conda-lock` to...

> * use `setup-miniconda` with `$CONDA` set to the unpacked env I am also trying to setup a GA with `setup-miniconda` and `conda-pack` but I don't get that part. Does...

> Interesting. We could defiitely add something like this, however using tokens feels better in general . I know but all our internal stack is login-based. It would be nice...

> There are some things to definel like where to install de the anaconda client package. I would say in the base env since the activated env is the one...

Hum no you could do the login directly within the action right? Then in whatever env you are you'll be logged to anaconda. Unless I am missing something?

`anaconda login` simply write a token in `~/.continuum/anaconda-client/tokens/`.

How do you deal when the same dep is defined multiple times? Does the order of the files matter? It's not exactly the same but I am also looking for...

The "Setup Conda" step when used with `mamba` seems to take a long time without installing my custom deps only `mamba-version` to `"*"` (~6 min). A `mamba` only setup would...

Same issue for me using mamba (without installing my deps during the action) and with the latest v2 version.