PR#2276: document merge modes - koji

koji

#2276 document merge modes

Merged 3 years ago by tkopecek. Opened 3 years ago by tkopecek.

tkopecek/koji issue2099 into master

extend docs

Tomas Kopecek • 3 years ago

e098d6d

document merge modes

Tomas Kopecek • 3 years ago

65b45ad

docs/source/external_repo_server_bootstrap.rst

file modified

+35 -4

		`@@ -38,6 +38,35 @@`
		`.. note::`
		`This uses $arch NOT $basearch`

		+ Koji behaves differently to the external repository based on which ``merge``
		+ mode is set for that. Merge modes can be set via ``-m`` option and are as
		`+ follows:`
		`+`
		+ ``koji``
		`+ Basic mode - koji expects, that that repo is complete and`
		`+ doesn't contain mixed content. It means that only rpms from one SRPM can`
		`+ be present in repo for given package.`
		`+`
		+ It runs ``mergerepos_c --koji`` Repositories generated via ``dist-repo``
		+ command (and all other repositories coming from koji` has these
		`+ properties.`
		`+`
		+ ``bare``
		+ It runs ``mergerepos_c --pkgorigins --all``. It includes all rpms with
		`+ same package name and architecture even if version or release is`
		+ different. This one is needed for modular repos. ``createrepo_c`` 0.14+
		+ compiled with ``libmodule`` support needs to be installed on the
		`+ builder. Nevertheless, only the first rpm with identical NEVRA is`
		`+ accepted.`
		`+`
		+ ``simple``
		+ It runs ``mergerepos_c --mode simple`` - we're least restrivtive with
		`+ this type of repo. Even packages with identical NEVRA are accepted in`
		+ such case. Simple mode is in ``createrepo_c`` suite from version 0.13.
		+ Reasons to use this compared to ``bare`` mode is a) you have older
		+ ``createrepo_c``, b) you really want to have all this identical NEVRAs
		`+ in the repo.`
		`+`
		`* Create a build target that includes the tags you've already created. ::`

		`$ koji add-target dist-foo dist-foo-build`
		`@@ -86,10 +115,12 @@`
		`Regenerating your repo`
		`======================`

		`- koji doesn't monitor external repositories for changes. new repositories`
		`- will be generated when packages you build land in a tag that populates`
		`- the buildroot or you manually regenerate the repository. you should be`
		`- sure to regularly regenerate the repositories manually to pick up`
		`+ koji doesn't monitor external repositories for changes by default.`
		+ Administrators can enable such bejaviour with setting ``check_external_repos =
		+ true`` in ``kojira.conf`` (for details see :doc:`utils.rst`). If it is not
		`+ enabled new repositories will be generated when packages you build land in a tag`
		`+ that populates the buildroot or you manually regenerate the repository. you`
		`+ should be sure to regularly regenerate the repositories manually to pick up`
		`updates.`

		`::`