A namespace is the part of Cloud where a user or organization
may host packages. For example, the user namespace
https://anaconda.org/travis contains packages that were uploaded
and shared by a user named travis.

macOS and Linux systems are Unix systems. Packages built for Unix systems
require a build.sh file, packages built for Windows require a
bld.bat file, and packages built for both Windows and Unix systems
require both a build.sh file and a bld.bat file. All packages
require a meta.yaml file.

To build the package, turn off automatic Client uploading
and then run the condabuild command:

condaconfig--setanaconda_uploadnocondabuild.

All packages built in this way are placed in a subdirectory of the
Anacondaconda-bld directory.

You can check where the resulting file was placed with the
--output option:

condabuild.--output

You can upload the test package to Cloud with the Anaconda
upload command:

anacondaloginanacondaupload/path/to/conda-package.tar.bz2

NOTE: Replace /path/to/ with the actual path where you
stored the package.

For more information on conda’s overall build framework, you may
also want to read the articles Building conda
packages.

To copy a package from the channel conda-forge to a personal channel such as jsmith:

anacondacopyconda-forge/glueviz/0.10.4--to-ownerjsmith

conda-forge/glueviz/0.10.4 is a “spec” and can match either of two formats:
user/package/version or user/package/version/filename.

Previously labels were called “channels”, and the anacondacopy command has deprecated
options from-channel and to-channel that expect to operate on labels. These deprecated
options should not be used. If you attempt to run
anacondacopy--from-channelconda-forge--to-channeljsmithglueviz, you will receive an
error that Labelconda-forgedoesnotexist.