A non-official clone of git-annex established for DataLad purposes. No PRs will be merged, but could be used to test perspective git-annex patches. Official git-annex repository: https://git.kitenet.net/index.cgi/git-annex.git/
16
stars
3
forks
source link
Update packages in client environments if necessary on every run #184
This requires all client environments to now use conda instead of regular virtual environments.
environment.yml had to be replaced with spec-file.txt because:
The --satisfied-skip-solve option (for exiting early if all package requirements are already met by the environment) is a practical necessity when updating; without it, conda will spend a lot of time fetching & resolving dependency information even if there's nothing to do.
--satisfied-skip-solve is an option on conda install and conda update but not on conda env update.
The --file option to conda create and conda install must be a spec file; YAML environment files are only supported by the conda env commands. In addition, conda update seems to use a third file format, but I can't figure out what it is.
Also, the code blocks in README.md were adjusted in order to avoid indentation in the rendered output while still aligning on multiples of four spaces.
@yarikoptic Is this the kind of commit message you're looking for?
yarikoptic
commented
10 months ago
Closes #182.
This requires all client environments to now use conda instead of regular virtual environments.
environment.ymlhad to be replaced withspec-file.txtbecause:The
--satisfied-skip-solveoption (for exiting early if all package requirements are already met by the environment) is a practical necessity when updating; without it, conda will spend a lot of time fetching & resolving dependency information even if there's nothing to do.--satisfied-skip-solveis an option onconda installandconda updatebut not onconda env update.The
--fileoption toconda createandconda installmust be a spec file; YAML environment files are only supported by theconda envcommands. In addition,conda updateseems to use a third file format, but I can't figure out what it is.Also, the code blocks in
README.mdwere adjusted in order to avoid indentation in the rendered output while still aligning on multiples of four spaces.@yarikoptic Is this the kind of commit message you're looking for?