![]() This seems like a successful "isolated" install and will keep conda nicely quarantined from wreaking havoc on my system.Ĭonda init doesn't do too much polluting. Installing in $HOME is definitely the easiest to manage.Īs long as I say no here, anaconda will not touch my dot files and I can just activate anaconda whenever I need by running source /bin/activate. I appreciate any insights :)Īs others said, use miniconda over the full anaconda. If I mess anything up, I feel confident I could do a clean reinstall and get back to here pretty quickly, however, I have sunk a lot of time into setting up this current build and would like to keep it clean and properly built. This is my first arch install and I have already learned so much about how everything interacts and works, but it is a lot to take in. Is that not as much of a threat with arch linux because of how easy it is to just uninstall and rebuild different packages as you need them? Thus we are just easily creating whatever environment we need as we need it? Im a bit confused. This would put conda in my /usr/opt/bin and /usr/opt/lib.but one of the main pieces of advice I read when reading about installing anaconda is to NEVER do a system wide install. HOWEVER, installing through AUR by definition is a sytemwide install. ![]() Building from AUR helps you stay consistent and keep everything in the same place. If you end up creating a mess and creating conflicts you can just uninstall anaconda and rebuild it from source whenever you need to run it. If you consistently build everything from AUR then pacman will keep track of everything for you. This seems like a successful "isolated" install and will keep conda nicely quarantined from wreaking havoc on my system.Īpproach 2 Don't follow their install, build from AUR: ![]() ![]() Furthermore there is a step where the ask "Do you wish the installer to initialize Anaconda3 by running conda init?” As long as I say no here, anaconda will not touch my dot files and I can just activate anaconda whenever I need by running source /bin/activate. This installs anaconda in my /home/charper/anaconda directory, so this is NOT system wide. It defeats the purpose of anaconda and that is exactly how things get messy! To follow this approach I would just install anaconda following the directions from their website. There seems to be two competing approaches to handling conda:Īpproach 1 Don't do a system-wide install of conda: I know that package managers can cause a huge mess in the organization of your system, so I was doing some research on the arch forums to discern a "best practice" for installing conda. Latest Miniconda Installer Links ¶ Latest - Conda 23.3.1 Python 3.10.I use a product called MFiX for research which must be installed through anaconda. Which does require administrator permissions. ![]() However, if you need to, you can install Miniconda system wide, Which does not require administrator permissions and is the most robust type of On Windows, macOS, and Linux, it is best to install Miniconda for the local user, Minimum 400 MB disk space to download and install.The linux-aarch64 Miniconda installer requires glibc >=2.26 and thus will not work with CentOS 7, Ubuntu 16.04, or Debian 9 (“stretch”).System architecture: Windows- 64-bit x86, 32-bit x86 macOS- 64-bit x86 & Apple M1 (ARM64) Linux- 64-bit x86, 64-bit aarch64 (AWS Graviton2), 64-bit IBM Power8/Power9, s390x (Linux on IBM Z & LinuxONE).If your operating system is older than what is currently supported, you can find older versions of the Miniconda installers in our archive that might work for you.Operating system: Windows 10 or newer, 64-bit macOS 10.13+, or Linux, including Ubuntu, RedHat, CentOS 7+, and others.License: Free use and redistribution under the terms of the EULA for Miniconda. ![]()
0 Comments
Leave a Reply. |