Skip to content

ipmrove install_substitutes #4117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 25, 2025
Merged

ipmrove install_substitutes #4117

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
58d9fa1
ipmrove install_substitutes
memsharded Jun 6, 2025
0e67fa8
Merge branch 'develop2' into fix/install_substitutes
czoido Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions reference/tools/system/package_manager.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,11 +68,12 @@ method<conan_tools_system_package_manager_apt>`.
architecture (the machine that will run the software), it has an effect when cross
building. This method will return the return code of the executed commands.
* ``install_substitutes(packages_substitutes, update=False, check=True)``: try to install
the list of lists of substitutes packages passed as a parameter, e.g., ``[["pkg1", "pkg2"], ["pkg3"]]``.
one of the lists of substitutes packages passed as a parameter, e.g., ``install_substitutes(["pkg1", "pkg2"], ["pkg3"])``.
It succeeds if one of the substitutes list is completely installed, so it's intended to be used when you have
different packages for different distros. Internally, it's calling the previous
``install(packages, update=update, check=check)`` method, so ``update`` and ``check`` have the same
purpose as above.
different packages for different distros. In this example, it will first try to install ``pkg1`` and ``pkg2``, if
it succeeds to install both packages, it will stop. If it fails, it will proceed to the next list and try to install ``pkg3``.
Internally, it's calling the previous ``install(packages, update=update, check=check)`` method, so ``update``
and ``check`` have the same purpose as above.
* ``update()`` update the system package manager database. Its behaviour is affected by
the value of ``tools.system.package_manager:mode``
:ref:`configuration<conan_tools_system_package_manager_config>`.
Expand Down