mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: understanding why standalone conda package gets preferred

Browse source
This commit is contained in:
Ilya_Shlyakhter 2020-08-27 15:32:09 +00:00 • committed by admin
parent 02a35c9cee
commit 22dc07e68f
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/forum/building_the_standalone_distribution_from_source/comment_12_9b0a7c108855d9db63092dd5f93bc5e5._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="understanding why standalone conda package gets preferred"
date="2020-08-27T15:32:05Z"
content="""
@cardoso-neto \"The only dependency that was installed when I conda-installed git-annex was this\" -- do you by chance remember the exact commands used to create that conda environment, before you tried installing git-annex into it? (Or if you have the environment, can you do `conda list --explicit` in it?) I'd like to better understand why `conda install` prefers the standalone package [so often](https://anaconda.org/conda-forge/git-annex/files). I'll ask conda gurus, but first need a reproducible case where that happens seemingly unnecessarily.
"""]]