ACP Conda Build & Distribution Flashcards

What command renders the final meta.yaml for a recipe after applying all variant substitutions, without actually building it?

Answer: conda render

`conda render` processes all Jinja2 templating and variant configs in a recipe and outputs the fully resolved meta.yaml without triggering a build.

In conda packaging terminology, what is a 'noarch' package?

Answer: A platform-independent package that installs on any OS/architecture

A `noarch` package (typically `noarch: python`) contains no compiled binaries and can be installed on any platform, eliminating the need to build per-OS variants.

Which command checks a built conda package for common packaging issues such as missing files or incorrect metadata?

Answer: conda inspect

`conda inspect` provides subcommands like `conda inspect linkages` and `conda inspect objects` to audit installed packages for linking issues and metadata correctness.

When a conda package recipe uses `{{ version }}` in meta.yaml, where is the value of `version` typically sourced from?

Answer: From a set statement at the top of meta.yaml using Jinja2 templating

Jinja2 `{% set version = '1.2.3' %}` at the top of meta.yaml assigns the variable, which is then referenced as `{{ version }}` throughout the recipe for DRY versioning.

What is the role of the `source` section in a conda meta.yaml recipe?

Answer: Specifies where to fetch the package source code (URL, git repo, or local path)

The `source` section tells conda-build where to download or copy the package source, supporting URLs with checksums, git repositories, and local directory paths.

After building a conda package locally, which flag do you use with `conda install` to install it directly from the local build output directory?

Answer: --use-local

The `--use-local` flag instructs conda to search the local package cache (typically `~/anaconda3/conda-bld/`) before checking remote channels.