Replace source activate by conda activate in conda install guide

[slel]

As reported by "dantetante"
on sage-devel,
the SageMath installation guide for conda
currently suggests

source activate sage

but this should be changed to

conda activate sage

For reference, this changed with the release of Conda 4.4.0, see the release notes:

• https://docs.conda.io/projects/conda/en/latest/release-notes.html

Depends on #27817

CC: @saraedum @slel

Component: documentation

Keywords: conda

Author: Dima Pasechnik

Branch: 50c84da

Reviewer: Volker Braun

Issue created by migration from https://trac.sagemath.org/ticket/27950

[dimpase]

comment:1

Thanks. I meant to add it to #27817 but forgot...

[dimpase]

Branch: #27817

[dimpase]

Changed branch from #27817 to none

[dimpase]

Dependencies: #27817

[dimpase]

comment:4

please review.

---

New commits:

0e329c9

updated conda installation details

[dimpase]

Commit: 0e329c9

[dimpase]

Branch: public/documentation/condainst

[dimpase]

Author: Dima Pasechnik

[slel]

comment:5

- dependicies resolution
+ dependency resolution

[dimpase]

comment:6

you're welcome do add a commit, it's a public branch :-)

[sagetrac-git]

Changed commit from 0e329c9 to ef292fe

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

ef292fe

fixed typo

[dimpase]

comment:8

fixed.

[slel]

comment:9

After doing

$ conda install mamba -c conda-forge # installs mamba

does something need to be done to make mamba work?
Running this directly

$ mamba create -n sage sage -c conda-forge # replaces "conda create..."

gives an error:

-bash: mamba: command not found

[slel]

comment:10

It seems to be a matter of letting conda tweak one's PATH vs not.

Running the following works for me (I installed Miniconda in /opt):

$ /opt/miniconda3/bin/mamba create -n sage sage -c conda-forge

Besides that: maybe add some actual date instead of |today| in:

At the time of this edit (|today|)

[dimpase]

comment:11

Replying to @slel:

After doing

$ conda install mamba -c conda-forge # installs mamba

does something need to be done to make mamba work?
Running this directly

$ mamba create -n sage sage -c conda-forge # replaces "conda create..."

gives an error:

-bash: mamba: command not found

it seems that your setup is non-standard (wrong conda is called ?). What I see that conda and mamba are installed into the same directory, and so whenever you have one in PATH, you have the other, too.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

50c84da

wrote the actual date in

[sagetrac-git]

Changed commit from ef292fe to 50c84da

[vbraun]

Reviewer: Volker Braun

[vbraun]

Changed branch from public/documentation/condainst to 50c84da

[slel]

Changed commit from 50c84da to none