docs/modules
Carl George 6a20481eb4 Clarify policy on non-default modules
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.
2026-07-06 20:22:26 -05:00
..
ROOT Clarify policy on non-default modules 2026-07-06 20:22:26 -05:00