Add variants_mode: local support to get a variants file for package - #158
Merged
Merged
Conversation
traversaro
requested review from
Tobias-Fischer,
baszalmstra,
wep21 and
wolfv
and removed request for
baszalmstra
September 30, 2026 15:49
baszalmstra
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #114 . This implements O2 in #114 (comment) .
This PR adds a
variants_modekey to vinca.yaml, that controls how rattler-build receives therepository-level
conda_build_config.yaml:global(default) leaves generated recipes unchanged. Builds must pass theroot configuration explicitly, for example with
rattler-build build ... -m ./conda_build_config.yaml.localgenerates avariants.yamlbeside everyrecipe.yaml. Vinca convertslegacy comment selectors to v1 selectors and keeps only pins used by that
package. Builds must not pass the root configuration with
-m, because anexplicit variant file takes precedence over the recipe-local file.
In case
variants_mode: localis used, it is possible to specify a per-packagevariant_overridesinpkg_additional_info.yaml:this permits to build only a subset of a packages with an higher
c_stdlib_version, as required for example in RoboStack/ros-jazzy#167 .Note that switching from
variants_mode: globaltovariants_mode: localrequires changing some files in theros-<distro>robostack repository, but does not strictly requires a full rebuild.