Remove conda from the setup scripts

[amolchanov86]

As the title says, it would be better if the installation script would identify if the user already has anaconda running and simply add env to it, rather than installing miniconda and adding env there.
Right now, I hack it by providing a symbolic link from ~/miniconda/envs/garage to ~/anaconda2/envs/garage but the proper fix would be appropriate.

[ryanjulian]

This is actually intentional because we only test with miniconda2, and we don't want to provide installation routines for configurations which we don't test.

I didn't see it as a bug, since anaconda/miniconda can coexist peacefully.

What do you think about instead providing an arg to the setup script which allows the user to specify an existing conda to use (along with a warning message that we haven't tested your conda)?

[amolchanov86]

I see. It is a workaround - I guess it will do the job. I mean it even works if I simply put a softlink :)
I am not sure why miniconda was a choice #1, I guess lightness was one factor.
The original rllab worked on anaconda, hence all the existing repos, i.e. from Chelsea and Tuomas are using anaconda (this is where I inherited the anaconda from as well).
Switching between them could indeed be done, it is just a matter of convenience for the user.

[ryanjulian]

yeah--we have to keep it light to keep the CI fast.

if you are advanced enough to already have your own conda, then i think the switch will be okay. we will need to update the documentation.

[amolchanov86]

Btw, one good update to documentation would be to add an explicit note that "if you are using anaconda, please follow the Manual installation" :)
I have just noticed that I shouldn't have used the express :)

[ryanjulian]

Okay, let's make that part of the scope for this issue.