Support package variants for dev packages #802
Draft
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.
Support package variants for dev packages
This allows compiling development packages partially (e.g. using a
non-standard CMake target) to save time when developing locally.
It also allows packages to depend on "variants" of other packages, e.g.
O2Physics -> O2#Analysis and O2sim -> O2#Simulation. aliBuild merges variants
if multiple are required, e.g. aliBuild build O2sim O2Physics in the above
case would build O2 with ALIBUILD_BUILD_VARIANT=Analysis,Simulation. "Full"
builds (no variants) always take precedence, and are the only possible
behaviour for non-development packages (e.g. to allow reusing tarballs as
before, and to avoid heisenbugs in CI).