attribute may specify a glob-like URL pattern for matching. Note that in this case, the HTTP schema must match exactly to the channel URL, so a pattern like * is not valid. allowlist_channels and denylist_channels: p.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example merely indicate managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory

attribute may specify a glob-like URL pattern for matching. Note that in this case, the HTTP schema must match exactly to the channel URL, so a pattern like * is not valid. allowlist_channels and denylist_channels: p.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example merely indicate managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory

attribute may specify a glob-like URL pattern for matching. Note that in this case, the HTTP schema must match exactly to the channel URL, so a pattern like * is not valid. allowlist_channels and denylist_channels: p.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example merely indicate managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory

attribute may specify a glob-like URL pattern for matching. Note that in this case, the HTTP schema must match exactly to the channel URL, so a pattern like * is not valid. auto_update_conda: Update conda automatically p.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example merely indicate managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory

attribute may specify a glob-like URL pattern for matching. Note that in this case, the HTTP schema must match exactly to the channel URL, so a pattern like * is not valid. auto_update_conda: Update conda automatically managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. 4.1. User guide 77 conda, Release 24.5.1.dev1 Package strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64

managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Windows. The placeholder may contain either "\" or "/" on Windows, but the replacement prefix will match the delimiter used in the placeholder. The default placeholder /opt/anaconda1anaconda2anaconda3 is

managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Windows. The placeholder may contain either "\" or "/" on Windows, but the replacement prefix will match the delimiter used in the placeholder. The default placeholder /opt/anaconda1anaconda2anaconda3 is

managing packages guide. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. Package specification Package metadata The info/ directory strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Windows. The placeholder may contain either "\" or "/" on Windows, but the replacement prefix will match the delimiter used in the placeholder. The default placeholder /opt/anaconda1anaconda2anaconda3 is

to manage packages. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. 8 Chapter 1. User guide conda, Release 23.7.4.dev7 1 1.3 Conda package specification • Package metadata • Repository structure and index • Package match specifications • Version ordering Package metadata The info/ directory contains all metadata about strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64

to manage packages. Learn more about package metadata, repository structure and index, and package match specifications at Package specifications. 8 Chapter 1. User guide conda, Release 23.9.1.dev1 1 1.3 Conda package specification • Package metadata • Repository structure and index • Package match specifications • Version ordering Package metadata The info/ directory contains all metadata about strings A list of dependency specifications, where each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64