doc: Clarify relationship to Koji
Fixes: https://pagure.io/pungi/issue/1143 JIRA: COMPOSE-3372 Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
This commit is contained in:
parent
8d00f56117
commit
a340663f00
@ -38,6 +38,14 @@ delegated to separate executables. *Pungi* just makes sure that all the
|
|||||||
commands are invoked in the appropriate order and with correct arguments. It
|
commands are invoked in the appropriate order and with correct arguments. It
|
||||||
also moves the artifacts to correct locations.
|
also moves the artifacts to correct locations.
|
||||||
|
|
||||||
|
The executable name ``pungi-koji`` comes from the fact that most of those
|
||||||
|
separate executables submit tasks to Koji that does the actual work in an
|
||||||
|
auditable way.
|
||||||
|
|
||||||
|
However unlike doing everything manually in Koji, Pungi will make sure you are
|
||||||
|
building all images from the same package set, and will produce even
|
||||||
|
deliverables that Koji can not create like YUM repos and installer ISOs.
|
||||||
|
|
||||||
|
|
||||||
Links
|
Links
|
||||||
=====
|
=====
|
||||||
|
Loading…
Reference in New Issue
Block a user