v0.4.2

What's Changed

• Fixes slim update and allows for version selection by @Nortamo in #32
• Features by @Nortamo in #33

• Automatically determine host os for base container
• Warn when group setting fails, and don't stop the installation
• Activate venv when forcing conda to be active
• Keep venv active for environments created from wrapped containers

Logic for venv activation:

• An existing conda-containerize installation is used to create a venv.
• If no variables are set, the venv will be active (not by explicit activation but by the virtue of being called -> equivalent by python standard ) in the container but the conda environment will not be in PATH.
• Setting CW_FORCE_CONDA_ACTIVATE will first activate the conda environment and then the virtual env on startup
  (This was done to reduce the complexity of manually shuffling around the PATH entries)
• The use case where you would want for both the venv and conda to be in PATH but for the conda environment not to be active is not considered or supported.

Full Changelog: v0.4.0...v0.4.2

v0.4.0

What's Changed

• Replace miniconda by miniforge
• Tykky shell convenience function to activate and deactivate environments

v0.3.3

What's Changed

• Automatically create output directory if it doesn't exist
• Increase context length of prints from 10 to 20

v0.3.2: Merge pull request #20 from CSCfi/no_hardcoded

Don't hardcode path to singularity

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.yml when doing an installation
• wrap-install no longer excludes the parent mount point when using apptainer.
• wrap-container will switch to using sh if bash is not found when generating the wrappers
• Nested invocations now work even if the switch between _bin and bin fails
• In place upgrades now possible even if installation is in use, but will print a warning.
• Enabling user ~/.condarc with CW_ENABLE_CONDARC has 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