Skip to content

Commit

Permalink
Editing FAQ 10 and 12
Browse files Browse the repository at this point in the history
  • Loading branch information
Marcus Bobar committed Oct 11, 2024
1 parent 75b54d3 commit faee93b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/post/2024-oct-anaconda-transition.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ To activate a single package you would run:

{{% accordion-item title="10. Will my scripts that depend on specific Anaconda packages break when switching to Miniforge?" id="faq-10" %}}

Yes, you will need to reinstall any packages previously installed from the Anaconda channel.
Scripts using Anaconda packages that are also available within miniforge may not break. However, any Anaconda packages that are not used soley for instructional purposes would be violating of the Anaconda license terms, so they would need to be reinstalled through a different channel or tool such as conda-forge or pip.

{{% /accordion-item %}}

Expand All @@ -140,7 +140,7 @@ The conda-forge channel is set as the default (and only) channel for Miniforge.

{{% accordion-item title="12. Can I still use the Anaconda repository with Miniforge?" id="faq-12" %}}

No, the Anaconda repository can no longer be used. Instead, you would use the conda-forge channel or another non-license restricted channel like the bioconda channel.
The Anaconda repository can only be used with miniforge provided that the packages are used strictly for instructional purposes.

{{% /accordion-item %}}

Expand Down

0 comments on commit faee93b

Please sign in to comment.