Skip to content

Conversation

@alexlarsson
Copy link
Member

This allows you to specify alternative builds in one manifest file.
You specify the alternative on the commandline like:
flatpak-builder --alt=NAME ...

And this then builds the manifest like normally, but with a different
cache base-name (so that both alternatives can be cached at the
same time). However, using the new "alt" option in BuildOption
and [only|skip]-alts options in modules and sources you can
affect what gets built and how. This is very similar to how
things can already be per-arch optional.

This allows you to specify alternative builds in one manifest file.
You specify the alternative on the commandline like:
  flatpak-builder --alt=NAME ...

And this then builds the manifest like normally, but with a different
cache base-name (so that both alternatives can be cached at the
same time). However, using the new "alt" option in BuildOption
and [only|skip]-alts options in modules and sources you can
affect what gets built and how. This is very similar to how
things can already be per-arch optional.
@alexlarsson
Copy link
Member Author

Hmm, maybe we should make this a multi-argument thing instead. Like --enable=feature1 --enable=feature2, and then enable-if: ["feature1"].

@matthiasclasen
Copy link
Contributor

--enable/disable feature sounds more future-proof to me

@rh-atomic-bot
Copy link

☔ The latest upstream changes (presumably 51fc2cb) made this pull request unmergeable. Please resolve the merge conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants