Skip to content

sous-chefs/yum-epel

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

yum-epel Cookbook

Cookbook Version CI State OpenCollective OpenCollective License

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS , CentOS Stream and Scientific Linux (SL), Oracle Linux (OL).

The yum-epel cookbook takes over management of the default repositoryids shipped with epel-release.

Below is a table showing which repositoryids we manage that are shipped by default via the epel-release package:

Repo ID EL 7 EL 8 EL 9 CentOS Stream 8 CentOS Stream 9
epel ✔️ ✔️ ✔️ ✔️ ✔️
epel-debuginfo ✔️ ✔️ ✔️ ✔️ ✔️
epel-next ✔️ ✔️
epel-next-debuginfo ✔️ ✔️
epel-next-source ✔️ ✔️
epel-next-testing ✔️ ✔️
epel-next-testing-debug ✔️ ✔️
epel-next-testing-source ✔️ ✔️
epel-source ✔️ ✔️ ✔️ ✔️ ✔️
epel-testing ✔️ ✔️ ✔️ ✔️ ✔️
epel-testing-debuginfo ✔️ ✔️ ✔️ ✔️ ✔️
epel-testing-source ✔️ ✔️ ✔️ ✔️ ✔️

Requirements

Platforms

  • RHEL/CentOS and derivatives

Chef

  • Chef 12.15+

Maintainers

This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit sous-chefs.org or come chat with us on the Chef Community Slack in #sous-chefs.

Cookbooks

  • none

Attributes

See individual repository attribute files for defaults.

Recipes

  • yum-epel::default Generates yum_repository configs for the standard EPEL repositories. By default the epel repository is enabled. For CentOS Stream, the epel-next repository is also enabled.

Usage Example

To disable the epel repository through a Role or Environment definition

default_attributes(
  :yum => {
    :epel => {
      :enabled => {
        false
       }
     }
   }
 )

Uncommonly used repositoryids are not managed by default. This is speeds up integration testing pipelines by avoiding yum-cache builds that nobody cares about. To enable the epel-testing repository with a wrapper cookbook, place the following in a recipe:

node.default['yum']['epel-testing']['enabled'] = true
node.default['yum']['epel-testing']['managed'] = true
include_recipe 'yum-epel'

More Examples

Point the epel repositories at an internally hosted server.

node.default['yum']['epel']['enabled'] = true
node.default['yum']['epel']['mirrorlist'] = nil
node.default['yum']['epel']['baseurl'] = 'https://internal.example.com/centos/7/os/x86_64'
node.default['yum']['epel']['sslverify'] = false

include_recipe 'yum-epel'

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers!

https://opencollective.com/sous-chefs#backers

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website.

https://opencollective.com/sous-chefs/sponsor/0/website https://opencollective.com/sous-chefs/sponsor/1/website https://opencollective.com/sous-chefs/sponsor/2/website https://opencollective.com/sous-chefs/sponsor/3/website https://opencollective.com/sous-chefs/sponsor/4/website https://opencollective.com/sous-chefs/sponsor/5/website https://opencollective.com/sous-chefs/sponsor/6/website https://opencollective.com/sous-chefs/sponsor/7/website https://opencollective.com/sous-chefs/sponsor/8/website https://opencollective.com/sous-chefs/sponsor/9/website