Consistent normal case instead of title case in xref titles
This commit is contained in:
parent
aaf5180926
commit
f618be18b0
11 changed files with 41 additions and 42 deletions
|
|
@ -1,26 +1,26 @@
|
|||
* xref:getting-started.adoc[How to Use EPEL]
|
||||
* xref:getting-started.adoc[How to use EPEL]
|
||||
** xref:available-packages.adoc[Available packages]
|
||||
** xref:epel-testing.adoc[The EPEL-testing repository]
|
||||
* xref:epel-package-request.adoc[Requesting a New Package]
|
||||
* xref:epel-communication.adoc[Get in Touch]
|
||||
* xref:epel-package-request.adoc[Requesting a new package]
|
||||
* xref:epel-communication.adoc[Communicating with EPEL]
|
||||
* xref:epel-help.adoc[Helping EPEL]
|
||||
** xref:epel-qa.adoc[EPEL QA/Testing]
|
||||
** xref:epel-packaging.adoc[Packaging]
|
||||
*** xref:epel-packaging-examples.adoc[Packaging Examples]
|
||||
** xref:epel-package-maintainers.adoc[Package Maintainers]
|
||||
*** xref:epel-packaging-examples.adoc[Packaging examples]
|
||||
** xref:epel-package-maintainers.adoc[Package maintainers]
|
||||
*** xref:epel-packagers-sig.adoc[Packagers Special Interest Group]
|
||||
*** xref:epel-about-next.adoc[EPEL-Next]
|
||||
*** xref:epel-about-playground.adoc[EPEL-Playground]
|
||||
*** xref:epel-package-maintainer-generic-description.adoc[EPEL Package Maintainer Generic Description]
|
||||
*** xref:epel-rhel-entitlements.adoc[RHEL Entitlements]
|
||||
* xref:epel-policy.adoc[Guidelines and Policies]
|
||||
*** xref:epel-package-maintainer-generic-description.adoc[EPEL package maintainer generic job description]
|
||||
*** xref:epel-rhel-entitlements.adoc[RHEL entitlements]
|
||||
* xref:epel-policy.adoc[Guidelines and policies]
|
||||
** xref:branches.adoc[Branches]
|
||||
** xref:epel-policy-updates.adoc[Updates]
|
||||
** xref:epel-policy-incompatible-upgrades.adoc[Incompatible Upgrades]
|
||||
** xref:epel-policy-retirement.adoc[Package Retirement]
|
||||
** xref:epel-policy-incompatible-upgrades.adoc[Incompatible upgrades]
|
||||
** xref:epel-policy-retirement.adoc[Package retirement]
|
||||
** xref:epel-policy-scl.adoc[Software Collections (SCL)]
|
||||
** xref:epel-policy-missing-sub-packages.adoc[Missing RHEL Sub-Packages]
|
||||
** xref:epel-policy-steering-committee.adoc[Steering Committee]
|
||||
** xref:epel-policy-missing-sub-packages.adoc[Missing RHEL sub-packages]
|
||||
** xref:epel-policy-steering-committee.adoc[Steering committee]
|
||||
* xref:epel-about.adoc[About EPEL]
|
||||
** xref:epel-about-history-philosophy.adoc[History and Philosophy]
|
||||
** xref:epel-about-history-philosophy.adoc[History and philosophy]
|
||||
* xref:epel-faq.adoc[FAQ]
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ Learn more about EPEL-Next on the following page:
|
|||
No. EPEL is purely a complementary repository that provide add-on packages.
|
||||
EPEL packages will not conflict with any of the channels that it builds against, with limited exceptions
|
||||
(see xref:epel-policy.adoc#conflicts_in_compat_packages[conflicts in compat packages]).
|
||||
Those specific channels are listed in the xref:epel-policy.adoc#_policy[EPEL Policy].
|
||||
Those specific channels are listed in the xref:epel-policy.adoc#_policy[EPEL policy].
|
||||
|
||||
It is permitted for EPEL to provide an alternative non-modular package to
|
||||
any package found only in a non-default RHEL module.
|
||||
|
|
@ -171,7 +171,7 @@ years. Your participation is vital for the success of this project.
|
|||
|
||||
Software and hardware vendors are encouraged to get involved in EPEL.
|
||||
For more information, read the xref:epel-about.adoc#isvihv_perspective[
|
||||
ISV/IHV Perspective].
|
||||
ISV/IHV perspective].
|
||||
|
||||
[[why_isnt_a_package_in_epel_9_when_it_is_in_epel_8]]
|
||||
=== Why isn't a package in EPEL 9 when it is in EPEL 8?
|
||||
|
|
@ -210,7 +210,7 @@ orphaned.
|
|||
If the package is added to RHEL it must be retired from EPEL as it is no longer
|
||||
an "extra package for enterprise linux". There is some automation in place to
|
||||
file a ticket to give the EPEL maintainer a heads up; see the
|
||||
xref:package-maintainers::Package_Retirement_Process.adoc#_epel[EPEL Package Retirement Process]
|
||||
xref:package-maintainers::Package_Retirement_Process.adoc#_epel[EPEL package retirement process]
|
||||
for more information.
|
||||
|
||||
|
||||
|
|
@ -493,7 +493,7 @@ Fedora.
|
|||
[[what_do_i_have_to_do_to_get_a_package_removed_from_epel]]
|
||||
=== What do I have to do to get a package removed from EPEL?
|
||||
|
||||
Please follow the xref:package-maintainers::Package_Retirement_Process.adoc[Package Retirement Process].
|
||||
Please follow the xref:package-maintainers::Package_Retirement_Process.adoc[Package retirement process].
|
||||
|
||||
[[what_do_i_need_to_do_if_i_need_to_get_a_updated_package_quickly_into_the_epel_proper]]
|
||||
=== What do I need to do if I need to get a updated package quickly into the EPEL proper?
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ There are many ways to join in and help out with EPEL. A few are listed below. I
|
|||
|
||||
== Maintaining packages ==
|
||||
|
||||
Package Maintainers update, fix bugs and improve packages in the EPEL collection. See the xref:epel-package-maintainers.adoc[EPEL Package Maintainers] page for more information on roles and how to join this group.
|
||||
Package Maintainers update, fix bugs and improve packages in the EPEL collection. See the xref:epel-package-maintainers.adoc[EPEL package maintainers] page for more information on roles and how to join this group.
|
||||
|
||||
== Testing and Quality Assurance ==
|
||||
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ page.
|
|||
EPEL strives to provide updates that are compatible and stable to
|
||||
compliment the Enterprise Linux packages it's built on. You can find a
|
||||
detailed list of updates policies on the xref:epel-policy-updates.adoc[EPEL
|
||||
Updates Policy page] as well as xref:epel-policy-incompatible-upgrades.adoc[a
|
||||
updates policy page] as well as xref:epel-policy-incompatible-upgrades.adoc[a
|
||||
page on incompatible updates when they absolutely can't be avoided].
|
||||
|
||||
[[rhel_entitlements_for_epel_package_maintainers]]
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ I would be happy to be a co-maintainer if you do not wish
|
|||
to build it on epel9 (FAS: <your FAS Id>).
|
||||
....
|
||||
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[stalled EPEL request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
|
||||
* Ticket Title:
|
||||
** Stalled EPEL package: <package>
|
||||
|
|
@ -167,7 +167,7 @@ The EPEL Packagers SIG would be happy to be a co-maintainer
|
|||
if you do not wish to build it on epel9.
|
||||
....
|
||||
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[stalled EPEL request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
|
||||
* Ticket Title:
|
||||
** Stalled EPEL package: <package>
|
||||
|
|
|
|||
|
|
@ -5,8 +5,7 @@ include::partial$attributes.adoc[]
|
|||
|
||||
== Missing-but-built examples
|
||||
|
||||
These examples are for the xref:epel-policy-missing-sub-packages.adoc#short_term[Missing RHEL Sub-Packages / Missing Built Sub-Packages
|
||||
/ Short Term policy].
|
||||
These examples are for the xref:epel-policy-missing-sub-packages.adoc#short_term[Missing RHEL sub-packages/missing built sub-packages/short term policy].
|
||||
|
||||
=== Missing-but-built workflow
|
||||
|
||||
|
|
@ -154,6 +153,6 @@ rm -rf %{buildroot}%{python3_sitearch}
|
|||
|
||||
== Missing un-built examples
|
||||
|
||||
These examples are for the xref:epel-policy-missing-sub-packages.adoc#missing_un-built_sub-packages[Missing RHEL Sub-Packages / Missing Un-Built Sub-Packages policy].
|
||||
These examples are for the xref:epel-policy-missing-sub-packages.adoc#missing_un-built_sub-packages[Missing RHEL sub-packages/missing un-built sub-packages policy].
|
||||
|
||||
//TODO:Put Examples and Tips Here
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Fedora packages.
|
|||
|
||||
All EPEL package dependencies (build-time or runtime)
|
||||
MUST ALWAYS be satisfiable within the Target Base
|
||||
(as defined by xref:epel-policy.adoc#_policy[EPEL Policy])
|
||||
(as defined by xref:epel-policy.adoc#_policy[EPEL policy])
|
||||
or EPEL itself.
|
||||
xref:packaging-guidelines::WeakDependencies.adoc[Weak package dependencies]
|
||||
are allowed on packages from other RHEL channels
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Create an EPEL package that only has the missing packages, or missing arches.
|
|||
** fedpkg retire 'EPEL-only package'
|
||||
* When/If the missing package(s) are added to RHEL CRB, retire your -epel package following the xref:epel-policy-retirement.adoc#process_package_in_rhel[EPEL retirement policy].
|
||||
|
||||
xref:epel-packaging-examples.adoc#_missing_but_built_examples[Short Term Examples and Workflow]
|
||||
xref:epel-packaging-examples.adoc#_missing_but_built_examples[Short term examples and workflow]
|
||||
|
||||
[[long_term]]
|
||||
=== Long term
|
||||
|
|
@ -85,4 +85,4 @@ You can create packages that supply missing sub-packages that were not built in
|
|||
In the past these were named <package>-extra, but these are now named <package>-epel to avoid confusion.
|
||||
|
||||
|
||||
xref:epel-packaging-examples.adoc#_missing_un_built_examples[Missing But Un-Built Examples]
|
||||
xref:epel-packaging-examples.adoc#_missing_un_built_examples[Missing but un-built examples]
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ include::partial$attributes.adoc[]
|
|||
|
||||
This document describes the policy for updates to packages in the EPEL
|
||||
package collection. For general EPEL package guidelines, refer to the
|
||||
xref:epel-policy.adoc[EPEL Guidelines and Policy] page.
|
||||
xref:epel-policy.adoc[EPEL guidelines and policy] page.
|
||||
|
||||
[[stable_releases]]
|
||||
== Stable releases
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ xref:packaging-guidelines::index.adoc#_naming[package naming guidelines], and th
|
|||
xref:packaging-guidelines::ReviewGuidelines.adoc[package review guidelines] that are designed
|
||||
and maintained by the xref:fesco::index.adoc[FESCo], and
|
||||
link:++https://fedoraproject.org/wiki/Packaging_Committee++[Packaging Committee]. EPEL-specific exceptions
|
||||
are documented here and in the xref:epel-packaging.adoc[EPEL Packaging] page.
|
||||
are documented here and in the xref:epel-packaging.adoc[EPEL packaging] page.
|
||||
|
||||
Please note that the sections "Guidelines" and "Policies" use their
|
||||
names on purpose. Consider the guidelines as something that should be
|
||||
|
|
@ -108,7 +108,7 @@ also promoted to stable. Update candidates that aren't pushed to stable after 6
|
|||
|
||||
For more information about updating EPEL packages, including minimum
|
||||
testing time for packages, refer to the xref:epel-policy-updates.adoc[EPEL
|
||||
Updates Policy].
|
||||
updates policy].
|
||||
|
||||
[[workflow_examples_information]]
|
||||
== Workflow examples/information
|
||||
|
|
@ -244,13 +244,13 @@ current Fedora releases. Sometimes there are changes in Fedora that
|
|||
cause the packaging guidelines there to not make sense for the older
|
||||
software being run in RHEL. When that occurs, we document the
|
||||
differences with the Fedora Packaging Guidelines on the
|
||||
xref:epel-packaging.adoc[EPEL Packaging] page.
|
||||
xref:epel-packaging.adoc[EPEL packaging] page.
|
||||
|
||||
[[policy_for_conflicting_packages]]
|
||||
== Policy for conflicting packages
|
||||
|
||||
xref:epel-faq.adoc#does_epel_replace_packages_provided_within_red_hat_enterprise_linux[Per
|
||||
RHEL Release Package Conflict Channel Exclusions]
|
||||
RHEL release package conflict channel exclusions]
|
||||
|
||||
* EPEL packages must not conflict with packages in the target base of RHEL.
|
||||
See above link for a complete list of channels per RHEL Release that EPEL does not conflict with.
|
||||
|
|
@ -272,8 +272,8 @@ needs to be removed from EPEL. Please follow the
|
|||
xref:package-maintainers::Package_Retirement_Process.adoc[retirement process] to do
|
||||
this. If the package is only available for a subset of all
|
||||
architectures, it might still be possible to keep the package in EPEL as
|
||||
described in the xref:epel-packaging.adoc#limited_arch_packages[EPEL Packaging
|
||||
Guidelines].
|
||||
described in the xref:epel-packaging.adoc#limited_arch_packages[EPEL packaging
|
||||
guidelines].
|
||||
|
||||
[[conflicts_in_compat_packages]]
|
||||
== Conflicts in compat packages
|
||||
|
|
@ -283,7 +283,7 @@ EPEL has a greater need for forward compat (i.e. newer alternate version) packag
|
|||
There may also be cases where backwards compat (i.e. older alternate version) packages are needed.
|
||||
When creating a compat package,
|
||||
note that it is okay to set a Conflicts between them as noted in the
|
||||
xref:packaging-guidelines::Conflicts.adoc#_compat_package_conflicts[Fedora Conflicts Guidelines].
|
||||
xref:packaging-guidelines::Conflicts.adoc#_compat_package_conflicts[Fedora conflicts guidelines].
|
||||
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.
|
||||
|
||||
|
|
@ -292,7 +292,7 @@ The latter is an explicit exception to the general rule for EPEL packages to not
|
|||
|
||||
EPEL follows the
|
||||
xref:fesco::Policy_for_orphan_and_retired_packages.adoc[Fedora
|
||||
Policy for Orphan and Retired Packages].
|
||||
policy for orphan and retired packages].
|
||||
|
||||
Unretiring an EPEL-only package requires a re-review.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,8 +13,8 @@ The goal of EPEL is to make high quality Fedora packages available for RHEL and
|
|||
|
||||
== Setting up EPEL
|
||||
|
||||
Learn more about getting started using EPEL on the xref:getting-started.adoc[How to Use EPEL]
|
||||
page. See also xref:available-packages.adoc[Available Packages] to see what packages
|
||||
Learn more about getting started using EPEL on the xref:getting-started.adoc[How to use EPEL]
|
||||
page. See also xref:available-packages.adoc[Available packages] to see what packages
|
||||
are available for each version.
|
||||
|
||||
[[what_is_extra_packages_for_enterprise_linux_or_epel]]
|
||||
|
|
@ -33,11 +33,11 @@ including buildsystem, Bugzilla instance, updates manager, mirror manager and mo
|
|||
|
||||
Learn more about EPEL in the following pages:
|
||||
|
||||
* link:epel-faq[EPEL FAQ]
|
||||
|
||||
* link:epel-about[About EPEL]
|
||||
|
||||
* link:epel-policy[EPEL Guidelines and Policies]
|
||||
* link:epel-policy[EPEL guidelines and policies]
|
||||
|
||||
* link:epel-faq[EPEL FAQ]
|
||||
|
||||
[[history_and_background_of_the_project]]
|
||||
== History and background of the project
|
||||
|
|
@ -48,5 +48,5 @@ great to also maintain add on packages for Enterprise Linux. Much of the
|
|||
early need was driven by what Fedora infrastructure needed on the RHEL
|
||||
machines that built and maintained Fedora. From there things have grown
|
||||
to a large collection of varied packages. See
|
||||
link:epel-about-history-philosophy[our history and Philosophy page] for
|
||||
link:epel-about-history-philosophy[our History and philosophy page] for
|
||||
more information.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue