- ...
- Now
conda-stage
asserts that Conda environments are successfully extracted and unpacked on the local disk. If it fails, then an informative error message is produced.
- Setting environment variable
CONDA_STAGE_ALLOW_BASE
totrue
re-enables support for auto-staging thebase
Conda environment. Use it with care and only if you understand that you cannot install new Conda packages into a staged environment.
- Support for auto-staging of the
base
Conda environment has been disabled, because it may cause confusion for those who have conda configured to automatically activate thebase
environment in their shell startup process. For example, when staged, it is not longer possible to install new Conda packages. Others may get 'WARNING: Cannot auto-stage Conda environment 'base', because 'conda-stage' not found'. We might revisit support for auto-staging of the 'base' environment at a later stage. It is still possible to manually stage, i.e.conda-stage --stage
.
- Add option
--prologue=<commands>
to be used together with--auto-stage=enable
for configuring auto-staging to call a set of commands before callingconda-stage
the first time. This can be useful whenconda-stage
is not on thePATH
, but needs to be loaded via an environment module first, e.g.--prologue="module load conda-stage"
. To set a default prologue command, use environment variable, e.g.CONDA_STAGE_PROLOGUE="module load conda-stage"
.
- Wrap URL in two of the warnings within brackets to avoid the following colon to be part of the URL.
- Cleanup:
conda-stage --auto-stage=enable
now only adds one file peractivate.d/
anddeactivate.d/
folder of the Conda environment. Previously, there was a second file used for optional debugging purposes.
- Now
conda-stage
detects if the cached 'conda-pack' tarball is out of date and re-packs it if needed.
- Staged Conda environment are now read-only by default. This was done to make it more clear that packages updates and installs should be done toward the original, non-staged environment.
-
Added
--writable
to make a Conda environment writable. This must be set when configuring the environment or when manually staging it. It cannot be done on an already staged environment. -
Using
--quiet
with--auto-stage=enable
will now make sure automatic staging during activation on the environment will be completely silent. -
An informative warning is now generated during staging if it is detected that the Conda environment has packages installed in its
pkgs/
folder. Such packages are not staged by conda-pack, cf. conda/conda-pack#112. -
Add option
--ignore-missing-files
which will be passed toconda-pack
as-is.
conda active <env>
on a fresh Conda environment '' configured to be auto-staged and without 'conda-pack' installed, would fail to be staged.
-
Added
conda-stage --stage
for staging of Conda environment. -
Now
conda-stage
defaults toconda-stage --help
. -
Now
conda-stage --stage
deactivates the original Conda environment before activating the staged one. Because of this, deactivation of the staged environment will no longer revert back to the original environment.
-
Add
conda-stage --auto-unstage=enable
to automatically unstage a staged Conda environment when deactivated. The default value of--auto-unstage
will be the same as--auto-stage
, if that is specified. To undo, callconda-stage --auto-unstage=disable
. -
Now
conda-stage --auto-stage=enable
removes the previously cached 'conda-pack' tarball, if it exists.
conda-stage --auto-stage=enable
could fail, because it did not created the '/etc/conda/activate.d/' folder.
- Renamed option
--readonly
to--read-only
.
- Add
conda-stage --auto-stage=enable
to automatically stage a conda environment when activated. Add--read-only
to stage a read-only environment. To undo, callconda-stage --auto-stage=disable
.
conda-stage --unstage
failed to remove read-only staged conda environments.
-
Add
conda-stage --pack
to runconda-pack
on an active conda environment and return. Together with--force
, this can be used to re-package an already packages environment. -
Report on progress when running
conda-pack
. This can be disabled with option--quiet
. -
Now verbose output has timing information for the different steps.
-
Now an error is produced if installation of conda-pack failed.
-
Now the 'conda-pack' tarball is created atomically by first outputting to a
.tmp.*.tar.gz
file, which is renamed to*.tar.gz
on success. This lowers the risk for ending up with a partially written*.tar.gz
due to user interrupts or disk failures. -
Now the 'conda-pack':ed tarball is extracted atomically by extracting to a
*.tmp/
folder, which is renamed to*/
on success. This lowers the risk for partially staged conda environments.
conda-stage()
choked on output message produced from installingconda-pack
. Now such output is redirected to standard error, which makes them also visible to the end user. This respects option--quiet
.
- When used by Conda, the command-line prompt is now the name of the
original Conda environment suffixed by an asterisk, e.g.
(myenv*)
.
-
Failed to install conda-pack automatically.
-
conda-stage()
would choke on progress output byconda-pack
.
- Add
conda-stage()
shell function for staging and unstaging conda environments on local disk.