Arch Linux User Repository

@bergentroll ok, I'll fix it in the next release.

petronny, that's right, but it is still OK to point BSD license: https://wiki.archlinux.org/index.php/PKGBUILD#license. E.g.: https://www.archlinux.org/packages/community/x86_64/bsd-games/. This way seems rather more informative.

@bergentroll custom means it doesn't match any license in /usr/share/licenses/common. So it's fine.

Why custom license? Isn't it under 3-clause BSD? https://docs.anaconda.com/anaconda/eula/

I'm not using it with sudo, in fact I'm not using it at all, I'm just opinionated.

But I tested what I thought would break and it's not as bad as I thought.

Because cloning really does make basically a new installation, upgrading Anaconda via the AUR does not mess with the existing clone. Though it would still make me wary.

Also, making a clone is essentially a completely separate installation not tracked by pacman, one which will not be updated when the AUR package updates. So it doesn't break, but you're also not gaining anything from using a package manager. It's even in your home directory (I didn't realise this).

Ok, maybe it's not so bad having this as an AUR package. It is still pretty odd, but I can see it might be a good workflow for some.

@chrisjbillington Another one using this package with sudo.
You shouldn't do that and please create a clone if you want to modify the environment.

$ conda create -n myroot --clone /opt/anaconda
$ source activate myroot
$ conda install pyqt

I really think Anaconda ought not to be an AUR package. It is a package manager and environment in its own right, and will leave files that are untracked by pacman, leading to advice elsewhere in this thread to install with --force to upgrade, and to clone the conda environment before installing packages. Neither of these are good ideas in the long run, as after an update or two to this AUR package, both will eventually break with files existing within the same directory that are for incompatible with each other with respect to compiler, Python version, or other things. You should install Anaconda exactly once (whether via this package or not) and then not update it from an AUR package, updating only with conda itself. Personally I would just put it in my home folder by running the installer from anaconda.org. pacman and the AUR add no extra value for this package, and it violates their assumptions of a package being a static set of files that can be upgraded.

it appears that anaconda is compiled w/o support for multiple processors. Is there a way for me to pass an argument like -j4 during install or anything. I have a 2-core 4-threads processor.

Anaconda3-5.3.0-Linux-x86_64.sh hash check failed.

@kbumsik @CaeZaR Build the package and install it with

$ pacman -U /path/to/anaconda.pkg.tar.xz --force

And you shouldn't use sudo conda to install things to /opt/anaconda. Create a clone and use it.

$ conda create -n myroot --clone /opt/anaconda
$ source activate myroot
$ conda install pyqt