CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs some small changes: 36 Chapter 4. "CONDA_PKGS_DIRS=%TMP%\conda-%RANDOM%" conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '.actions.FETCH[] | .url + "#"␣ ˓→+ .md5' >> explicit.txt set "CONDA_PKGS_DIRS=" The resulting explicit.txt can be used to update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you

CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs some small changes: 36 Chapter 4. "CONDA_PKGS_DIRS=%TMP%\conda-%RANDOM%" conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '.actions.FETCH[] | .url + "#"␣ ˓→+ .md5' >> explicit.txt set "CONDA_PKGS_DIRS=" The resulting explicit.txt can be used to update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you

CONDA_PKGS_DIRS=$(mktemp -d) conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '. ˓→actions.FETCH[] | .url + "#" + .md5' >> explicit.txt The syntax in Windows only needs some small changes: 36 Chapter 4. "CONDA_PKGS_DIRS=%TMP%\conda-%RANDOM%" conda create --dry-run MATCHSPECS_GO_HERE --json | jq -r '.actions.FETCH[] | .url + "#"␣ ˓→+ .md5' >> explicit.txt set "CONDA_PKGS_DIRS=" The resulting explicit.txt can be used to update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you

update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you in that location: conda search -c file:///opt/channel/ --override-channels � Note • The channel URL does not include the platform, as conda automatically detects and adds the platform. • The option listed here, in the order given. # Use "defaults" to automatically include all default channels. # Non-url channels will be interpreted as Anaconda.org usernames # (this can be changed by modifying the channel_alias

update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you in that location: conda search -c file:///opt/channel/ --override-channels Note: • The channel URL does not include the platform, as conda automatically detects and adds the platform. 4.1. User guide listed here, in the order given. # Use "defaults" to automatically include all default channels. # Non-url channels will be interpreted as Anaconda.org usernames # (this can be changed by modifying the channel_alias

update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you in that location: conda search -c file:///opt/channel/ --override-channels Note: • The channel URL does not include the platform, as conda automatically detects and adds the platform. 4.1. User guide listed here, in the order given. # Use "defaults" to automatically include all default channels. # Non-url channels will be interpreted as Anaconda.org usernames # (this can be changed by modifying the channel_alias

update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you in that location: conda search -c file:///opt/channel/ --override-channels Note: • The channel URL does not include the platform, as conda automatically detects and adds the platform. 4.1. User guide listed here, in the order given. # Use "defaults" to automatically include all default channels. # Non-url channels will be interpreted as Anaconda.org usernames # (this can be changed by modifying the channel_alias

following keys are added to info/ about.json if present in the build recipe: • home • dev_url • doc_url • license_url • license • summary • description • license_family info/recipe A directory containing use of key-value pairs. Standard specification channel (Optional) Can either be a channel name or URL. Channel names may include letters, numbers, dashes, and underscores. 22 Chapter 4. Contributors welcome ExactStrMatch - subdir # validated via ExactStrMatch - track_features # validated via FeatureMatch - url # validated via ExactStrMatch - version # validated via VersionSpec Key-value pair notation can be

update. 4. To test custom channels, serve the custom channel using a web server or using a file:// URL to the channel directory. Test by sending a search command to the custom channel. Example: if you in that location: conda search -c file:///opt/channel/ --override-channels Note: • The channel URL does not include the platform, as conda automatically detects and adds the platform. 4.1. User guide listed here, in the order given. # Use "defaults" to automatically include all default channels. # Non-url channels will be interpreted as Anaconda.org usernames # (this can be changed by modifying the channel_alias

following keys are added to info/ about.json if present in the build recipe: • home • dev_url • doc_url • license_url • license • summary • description • license_family info/recipe A directory containing use of key-value pairs. Standard specification channel (Optional) Can either be a channel name or URL. Channel names may include letters, numbers, dashes, and underscores. 22 Chapter 4. Contributors welcome ExactStrMatch - subdir # validated via ExactStrMatch - track_features # validated via FeatureMatch - url # validated via ExactStrMatch - version # validated via VersionSpec Key-value pair notation can be