modules/fm-orchestrator
1
0
Fork 0
mirror of https://pagure.io/fm-orchestrator.git synced 2026-02-02 20:59:06 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Mention layered product modules in KojiResolver.

Browse Source
This commit is contained in:
Jan Kaluza
2019-11-04 14:01:55 +01:00
parent 1c645f5a04
commit 566164ecb1
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/KOJI_RESOLVER.rst
View File

@@ -64,3 +64,19 @@ available modules to be used as buildrequires as follows:
buildrequires, and therefore, also as input to Module Stream Expansion. buildrequires, and therefore, also as input to Module Stream Expansion.
- It reuses already built components only from the modules tagged in the tag defined in - It reuses already built components only from the modules tagged in the tag defined in
``koji_tag_with_modules``. ``koji_tag_with_modules``.
Defining Layered Products Using KojiResolver
============================================
Sometimes it is needed to define a "layered product" on top of an existing base module.
A layered product is a special module that extends a base module. The goal of a layered product is
to allow building modules on top of an existing base module, but to not tag such module builds back
to the original base module's Koji tag. The module builds built for a layered product are therefore,
separated from the base module.
Defining a layered product using KojiResolver is simple. One just needs to create a new Koji
tag for the layered product which inherits the base module's Koji tag. There also needs to be
a new base module defined using the virtual modules MBS feature. This virtual module needs
to point to this newly created layered product's Koji tag. This virtual module should not
buildrequire a base module on the modulemd file level. This dependency is expressed using
Koji tag inheritance.