ODKRunner 0.2.1

Changes since version 0.2.0:

• If the image name (given to the --image option on the command line, or the ODK_IMAGE option in a run.sh.conf file) is unqualified, the obolibrary/ qualifier is automatically prepended (so, --image odklite is equivalent to --image obolibrary/odklite).
• Support for sharing the host’s local OAK cache directory with the container:
  • If the --oak-cache (-k) option is set to user, the user’s own OAK cache directory (by default ~/.data/oaklib, but it may be located elsewhere depending on the local Pystow configuration) is bound to /home/odkuser/.data/oaklib, so that any OAK command invoked within the container will benefit from the user’s cache.
  • If the option is set to repo, the variable OAKLIB_HOME will be set to /work/src/ontology/tmp/oaklib and exported into the container’s environment, so that any OAK command invoked within the container will use the tmp/oaklib directory as its cache. This is only effective when odkrun is started from within the src/ontology directory of an ODK repository; otherwise the option is ignored.
  • If the option is set to any other value, the value is interpreted as a path to an arbitrary directory on the host, which is bound to /home/odkuser/.data/oaklib within the container (so, --oak-cache user is in fact equivalent to --oak-cache ~/.data/oaklib, assuming the OAK cache is in its default location).
  • The -K option is a shorthand for --oak-cache user.
  • The option ODK_SHARE_OAK_CACHE, if found within a run.sh.conf file, is interpreted in the same way as the --oak-cache CLI option.