ACP ACP Conda Build & Distribution

Question 1

What file is required at the root of a conda package recipe to define its build metadata and dependencies?

Accepted Answer

meta.yaml

Answer

The meta.yaml file is the recipe descriptor that defines package name, version, source, build requirements, and runtime dependencies for conda-build.

Question 2

Which conda-build command is used to build a package from a local recipe directory called `my-package`?

Accepted Answer

conda-build my-package

Answer

Running `conda-build my-package` processes the recipe in that directory and produces a .tar.bz2 or .conda artifact.

Question 3

In a meta.yaml recipe, where do you specify packages that are needed ONLY during the build process (e.g., compilers)?

Accepted Answer

requirements: build

Answer

The `requirements: build` section lists cross-compilation tools and compilers that run on the build machine but are not needed in the final environment.

Question 4

What does the `conda convert` command allow you to do with an existing conda package?

Accepted Answer

Repackage a built artifact for a different platform/OS

Answer

`conda convert` repackages a compiled conda artifact for alternative platforms (e.g., from linux-64 to osx-64) when no compiled C extensions are involved.

Question 5

Which Anaconda-hosted service allows you to upload and share your built conda packages publicly or within a team?

Accepted Answer

Anaconda.org

Answer

Anaconda.org (formerly Binstar) is the cloud repository where users and organizations can upload, manage, and share conda packages and channels.

(ACP) Anaconda Certified Professional Practice Test

(ACP) Anaconda Certified Professional Practice Test

ACP ACP Conda Build & Distribution