custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. • Some Linux distros, such as Linux Mint, require a restart (shell restart, or logout/system version 1.6 3.1.1 Known installation issues with pip • When Conan is installed with pip install --user , usually a new directory is created for it. However, the directory is not appended automatically

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. • Some Linux distros, such as Linux Mint, require a restart (shell restart, or logout/system version 1.6 3.1.1 Known installation issues with pip • When Conan is installed with pip install --user , usually a new directory is created for it. However, the directory is not appended automatically

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Install configurations: $ conan config install # Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and Download a package, if it isn’t already in the local cache: $ conan install /@[<user>/#] [-r=] # Download␣ ˓→dependencies from only the specified remote

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. • Some Linux distros, such as Linux Mint, require a restart (shell restart, or logout/system version 1.6 3.1.1 Known installation issues with pip • When Conan is installed with pip install --user , usually a new directory is created for it. However, the directory is not appended automatically

custom configuration. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. • Some Linux distros, such as Linux Mint, require a restart (shell restart, or logout/system version 1.6 3.1.1 Known installation issues with pip • When Conan is installed with pip install --user , usually a new directory is created for it. However, the directory is not appended automatically