livery.extensions.conan._answers¶
livery.extensions.conan._answers ¶
The conan extension's answers about a package, from its recipe.
Functions:
| Name | Description |
|---|---|
current_version |
The version the recipe's |
version_files |
The recipe, |
requirements |
The conan references the recipe requires, each name to its version range. |
requirement_writers |
The recipe's writer of a requirement on a sibling that is a conan package. |
distributions |
The conan package the recipe releases, as its ecosystem and its name. |
registry |
The conan target the recipe's package goes to, as a probe of its versions. |
Attributes:
| Name | Type | Description |
|---|---|---|
ECOSYSTEM |
|
current_version ¶
The version the recipe's version attribute declares.
A consumer's recipe, one that names no reference, declares no version: it answers empty, which leaves the version to the set's other answers.
Source code in packages/extensions/conan/src/livery/extensions/conan/_answers.py
version_files ¶
The recipe, conanfile.py, the one file the version lives in.
Empty for a consumer's recipe, one that names no reference: no version lives in it.
Source code in packages/extensions/conan/src/livery/extensions/conan/_answers.py
requirements ¶
The conan references the recipe requires, each name to its version range.
requirement_writers ¶
requirement_writers(package: Package) -> tuple[RequirementWriter, ...]
The recipe's writer of a requirement on a sibling that is a conan package.
distributions ¶
The conan package the recipe releases, as its ecosystem and its name.
A recipe that declares both name and version names a
reference and releases the package; a consumer's recipe,
requirements alone, releases nothing, so it answers empty.
Source code in packages/extensions/conan/src/livery/extensions/conan/_answers.py
registry ¶
registry(package: Package) -> ConanRegistry | None
The conan target the recipe's package goes to, as a probe of its versions.
The target is the one the registry ladder resolves for conan in the package's workspace (livery.workshop.registry): a conan remote, a folder, or the forge's releases. A consumer's recipe releases nothing, so it answers None.