66a127c313
A module build can create packages that are tagged in the content tag, but should not be included in the module. Originally Pungi didn't know what exactly the module contains and so it needed to apply filters to exclude stuff that was definitely out. With getting the final MMD from Koji, we can actually make this a bit more strict by only keeping packages that we know we need. When processing each content tag, we can put into package set only packages that are included in some module using that tag. This should work with -devel modules as well. Both the regular and -devel modules will contribute to the set and thus all packages will go to the package set. Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com> |
||
|---|---|---|
| .. | ||
| sources | ||
| __init__.py | ||
| common.py | ||
| pkgsets.py | ||
| source.py | ||