doc: explain tradeoffs with pkgset_allow_reuse
Explain why someone would want to enable or disable the pkgset_allow_reuse option. Signed-off-by: Ken Dreyer <kdreyer@redhat.com>
This commit is contained in:
parent
d3acb0fa9e
commit
5ed5646bca
@ -507,7 +507,11 @@ Options
|
|||||||
|
|
||||||
**pkgset_allow_reuse** = True
|
**pkgset_allow_reuse** = True
|
||||||
(*bool*) -- When set to ``True``, *Pungi* will try to reuse pkgset data
|
(*bool*) -- When set to ``True``, *Pungi* will try to reuse pkgset data
|
||||||
from the old composes specified by ``--old-composes``.
|
from the old composes specified by ``--old-composes``. When enabled, this
|
||||||
|
option can speed up new composes because it does not need to calculate the
|
||||||
|
pkgset data from Koji. However, if you block or unblock a package in Koji
|
||||||
|
(for example) between composes, then Pungi may not respect those changes
|
||||||
|
in your new compose.
|
||||||
|
|
||||||
|
|
||||||
Example
|
Example
|
||||||
|
Loading…
Reference in New Issue
Block a user