However, in your conda recipe build.sh, would it be possible to switch from
python setup.py install
to
python setup.py install --single-version-externally-managed --record=record.txt
Right now, the install creates a .pth file and a egg file - it is not that these are wrong, but they are not recommended for conda environment management. I started a discussion here
to get some clarification about it. I think egg files are discouraged because it is harder to track things like file collisions between packages - the recommended way allows conda to track the packages better, I think.
I've been looking into adding cbf to the conda environments we maintain at LCLS, @chucki82 is using them locally (some work on this https://github.com/slaclab/anarel-manage/issues/4)
However, in your conda recipe build.sh, would it be possible to switch from
python setup.py install
topython setup.py install --single-version-externally-managed --record=record.txt
Right now, the install creates a .pth file and a egg file - it is not that these are wrong, but they are not recommended for conda environment management. I started a discussion herehttps://groups.google.com/a/continuum.io/forum/#!topic/conda/XFN2Lhm1ECE
to get some clarification about it. I think egg files are discouraged because it is harder to track things like file collisions between packages - the recommended way allows conda to track the packages better, I think.