You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the Conda configuration .condarc file is stored in a location outside of all Conda installations and is applied to all Conda environments.
MicroDrop requires packages that are available in the default Conda channels, but are instead provided in channels such as conda-forge, wheeler-microfluidics, etc. Therefore, it would be helpful to have such channels added to the .condarc Conda configuration.
Notes
Fortunately, Conda provides support for a system configuration file per Conda installation, by including a .condarc file in the root of a Conda installation (i.e., <Conda prefix>/.condarc).
Create a .condarc configuration including channels required for MicroDrop
Ideally, the list channels of channels could be customized to allow, for example, nightly/unstable installer builds using unstable source channels (e.g., paver build_installer -c <channel> -c <channel>)
Use post_install in .miniconda-recipe/construct.yaml to write .condarc to Conda prefix upon installation.
Other thoughts
Maybe we should try to use a similar mechanism to (1.1) above to specify a custom list of channels in the construct.yaml configuration?
Should the custom override the channels section in the construct.yaml file?
Maybe use --override-channels flag to define behaviour?
The text was updated successfully, but these errors were encountered:
With conda 4.2, add an additional .condarc file in the root of your active env (contents of CONDA_PREFIX environment variable) or set the CONDARC environment variable to the config you want to add.
All config information is now merged, with information "closer to the end" having precedence. General system locations -> user home directory -> environment-specific directories -> environment variable -> command line parameters
Questions
How is the channel priority resolved when the same channels are listed in different orderings between these .condarc files?
Motivation
By default, the Conda configuration
.condarc
file is stored in a location outside of all Conda installations and is applied to all Conda environments.MicroDrop requires packages that are available in the default Conda channels, but are instead provided in channels such as
conda-forge
,wheeler-microfluidics
, etc. Therefore, it would be helpful to have such channels added to the.condarc
Conda configuration.Notes
Fortunately, Conda provides support for a system configuration file per Conda installation, by including a
.condarc
file in the root of a Conda installation (i.e.,<Conda prefix>/.condarc
).There is also support (see
allow_other_channels
) for optionally allowing users to supplement the channels defined in the system.condarc
.Proposed solution
During the build of a MicroDrop installer:
.condarc
configuration including channels required for MicroDroppaver build_installer -c <channel> -c <channel>
)post_install
in.miniconda-recipe/construct.yaml
to write.condarc
to Conda prefix upon installation.Other thoughts
construct.yaml
configuration?channels
section in theconstruct.yaml
file?--override-channels
flag to define behaviour?The text was updated successfully, but these errors were encountered: