epel/docs
8
0
Fork 4
Code Pull requests 4 Projects Activity

Clarify policy for -epel suffixed packages

Browse source 
https://pagure.io/epel/issue/322
This commit is contained in:
Carl George 2026-01-14 22:12:17 -06:00
commit 53940beff0
2 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/epel-policy-missing-sub-packages.adoc
View file

@ -20,7 +20,7 @@ procedures have been setup.
[[shared_guidelines]]
== Shared guidelines
* You MUST name your source package `<package>-epel`
* You MUST name your source package `<package>-epel` per the xref:epel-policy.adoc#policy_for_epel_suffixed_packages[policy for `-epel` suffixed packages]
* You MUST NOT conflict with any RHEL packages or files
[[missing_built_sub-packages]]

8
modules/ROOT/pages/epel-policy.adoc
View file

@ -287,6 +287,14 @@ xref:packaging-guidelines::Conflicts.adoc#_compat_package_conflicts[Fedora confl
This is allowed both between EPEL packages and between EPEL and RHEL packages.
The latter is an explicit exception to the general rule for EPEL packages to not conflict with target base RHEL packages.
[[policy_for_epel_suffixed_packages]]
== Policy for `-epel` suffixed packages
The `-epel` suffix on package names is reserved for EPEL-only packages that provide
xref:epel-policy-missing-sub-packages.adoc[missing RHEL subpackages].
Any other use of the `-epel` suffix requires an explict exception from the
xref:epel-policy-steering-committee.adoc[EPEL Steering Committee].
[[policy_for_orphan_and_retired_packages]]
== Policy for orphan and retired packages