Tykky v0.3.0
Changelog
- When creating a venv from a conda installation, conda is no longer activated unless forced with
CW_FORCE_CONDA_ACTIVATE - System site packages can now be enabled when using pip-containerize with the flag
--system-site-packages - Version information is now saved in
share/VERSION.ymlwhen doing an installation wrap-installno longer excludes the parent mount point when using apptainer.wrap-containerwill switch to usingshifbashis not found when generating the wrappers- Nested invocations now work even if the switch between
_binandbinfails - In place upgrades now possible even if installation is in use, but will print a warning.
- Enabling user ~/.condarc with
CW_ENABLE_CONDARChas been documented.
Non isolated installation are now composable by adding their correct image mount path to CW_EXTRA_BIND_MOUNTS.
This enables calling software from Tykky installation A even if installation B was the one to start the container.
Enables e.g users to use Tykky to install snakemake using conda and then call other Tykky installed software in their workflow transparently.
New feature so Mileage may vary