Closed fiendish closed 9 years ago
Better would be to remove the virtualenv install script. It serves very little purpose and is just likely to not work sometimes.
Simplest is to just do
virtualenv --no-site-packages crosscat_env
source crosscat_env/bin/activate
cd crosscat_env
git clone https://github.com/mit-probabilistic-computing-project/crosscat.git
pip install -I -r crosscat/requirements.txt
python crosscat/setup.py install
Hi fiendish,
FYI: last I was working on crosscat, I don't think I was using virtualenv at all: it caused a lot of issues with jenkins scripts and the need for virtualenv was highly reduced when VM's were being built (now Docker containers as far as I know).
Note that scripts/install_scripts/install.sh does a straight 'pip install'. I don't think anything references virtualenv_setup.sh any more.
Best Dan
We do use virtualenvs for systems where the user has no admin privileges to install supporting packages like docker.io or virtualbox. But it's true that we don't need an included script for it, since the process is so trivial.
We removed all these scripts. Virtualenvs and Ubuntu 14.04 packages work fine for Crosscat now -- just use pip install .
if you want a pipply installation.
virtualenv setup script is looking for an install script that doesn't exist. I assume that it's trying to run an old equivalent of the pip requirements file.