The separate packages per-module features allows you to ,e.h., build separate packages for apache and webalizer. But, in the %post of the spec files the module is inserted. If webalizer has requires {} blocks that need apache types, the transaction will fail and the module will not be present on the installed system until it is manually loaded from /usr/share/selinux/...
The hard part is that we effectively templatize the entire sub-package in the spec file so there is no wau to state that a specific sub-package Requires: another sub-package.
The separate packages per-module features allows you to ,e.h., build separate packages for apache and webalizer. But, in the %post of the spec files the module is inserted. If webalizer has requires {} blocks that need apache types, the transaction will fail and the module will not be present on the installed system until it is manually loaded from /usr/share/selinux/...
The hard part is that we effectively templatize the entire sub-package in the spec file so there is no wau to state that a specific sub-package Requires: another sub-package.