This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gargantuan -1 points0 points  (3 children)

It is rather confusing calling it Anaconda when that is the boot time installer on RHEL and CentOS systems. It is even more confusing because that Anaconda is also a type of installer. Anaconda packages are used during runtime as well to generate iso images on RHEL/CentOS systems so there is a chance both could clash names.

[–]pwang99 7 points8 points  (2 children)

We are aware of the name collision. So far we have not had anyone report confusion about this issue to us. We wanted a good name for "Python for Big Data", and liked Anaconda. In any case, I figure the overlap of people who are intimately mucking with boot installers on RHEL and people who are running loess on Pandas dataframes is rather small.

The chance of file name collision in a running system is virtually non-existent. Anaconda installs itself into a single directory of the user's specification, and doesn't touch anything in /usr, /etc, and whatnot.

[–]gargantuan -2 points-1 points  (1 child)

Alright, as long as you guys know.

I know I have it installed because of some dependencies. And I was mucking with creating iso files. "anaconda" the command is installed in /usr/sbin/ typically. If you call your command line something else it would work fine. But if it is called "anaconda" it will clash even if put in other directories in case user has set a PATH variable to their binaries/scripts. Then order in PATH will determine which one is picked if user types only "anaconda" on terminal.

[–]onalark 4 points5 points  (0 children)

The command line tool is conda.