ostree: Add force_new_commit option

Followup from discussion in: https://pagure.io/pungi/issue/811

It's likely now that for Fedora Atomic Host we'll use this, to work
around other issues, after we fix the FAW change detection.

Signed-off-by: Colin Walters <walters@verbum.org>
This commit is contained in:
Colin Walters 2017-12-05 05:51:43 -05:00 committed by Ondrej Nosek
parent 5cc54cd587
commit 161b7f974b
3 changed files with 9 additions and 0 deletions

View file

@ -1220,6 +1220,9 @@ repository with a new commit.
deliverable is not release blocking.
* ``update_summary`` -- (*bool*) Update summary metadata after tree composing.
Defaults to ``False``.
* ``force_new_commit`` -- (*bool*) Do not use rpm-ostree's built in change
detection.
Defaults to ``False``.
* ``version`` -- (*str*) Version string to be added as versioning metadata.
If this option is set to ``!OSTREE_VERSION_FROM_LABEL_DATE_TYPE_RESPIN``,
a value will be generated automatically as ``$VERSION.$RELEASE``.