Difference between revisions of "Koji Testbed"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 63: | Line 63: | ||
=== Terminology === | === Terminology === | ||
| + | The most confusing word in Koji context is the word 'package', which means two related but very different things: | ||
| + | # the base name of a package, as colloquially used in a sentence like: �Hey, is lcmaps installed on this box?� | ||
| + | # the full ''name-version-release'' or NVR of the package, such as lcmaps-1.6.1-2.el6. | ||
| + | |||
| + | With that out of the way, the central structural element in Koji is the ''tag''. This is, of course, just a name, but many things can have tags attached to them. In fact, it is easier to reverse the idea of sticking a tag onto something and rather think of tags as pinboards where stuff is tacked onto. Here is a list of things that can go on tags: | ||
| + | |||
| + | * packages, in the first sense as described above | ||
| + | * packages, in the second sense as described above | ||
| + | * groups (we'll get to those later) | ||
| + | * external repositories | ||
| + | * other tags called �parents� | ||
| + | |||
| + | The second most confusing word in Koji context is the word 'parent' and, along with that, the entire concept of inheritance. In the biological sense we can't choose, change, or add parents, but tags have no such limitations. While normally we inherit from our parents after they pass away, tags inherit everything from all of their parents (and parents' parents) immediately. Remember: in the graphical displays, Koji shows parents down and to the right in the inheritance tree. | ||
The builds are done against targets, which have source and target tags, which have buildroots populated from repositories. The initial buildroots are set up from virtual packages called 'build' and 'srpm-build' created in koji. | The builds are done against targets, which have source and target tags, which have buildroots populated from repositories. The initial buildroots are set up from virtual packages called 'build' and 'srpm-build' created in koji. | ||
| Line 69: | Line 82: | ||
koji add-tag-inheritance --maxdepth 1 --priority 2 dist-fc18-build dist-fc17-build | koji add-tag-inheritance --maxdepth 1 --priority 2 dist-fc18-build dist-fc17-build | ||
| − | (I'm not too sure | + | (I'm not too sure what maxdepth and priority mean here; but Fedora's own koji lists the build group for FC18 as going all the way back to FC9.) |
=== Steps to follow if you need to do this from scratch === | === Steps to follow if you need to do this from scratch === | ||
