It's not technically not possible for EPEL packages to have build dependencies on non-default module packages. It is however technically possible for EPEL packages to have runtime dependencies on such packages. Doing so is a poor user experience because the package would fail to install by default, and would only install once a particular module stream is enabled. To avoid this situation, let's clarify the policy that such runtime dependencies are not allowed. |
||
|---|---|---|
| .. | ||
| assets/images | ||
| examples | ||
| pages | ||
| partials | ||
| nav.adoc | ||