The same pattern works fine for EPEL, but I switched back to using REPOTRACK for EPEL, because I rarely utilize more than a few hundred MB of the EPEL packages and finally got around to parsing out a list.

“rs32-reposync-update.sh” # for getting base, updates, and extras.

“rs64-reposync-update.sh” # for getting base, extras

And, a REPOTRACK script for getting selected packages from EPEL:

“rt64-c7x64-update.sh”

An easy way to begin using REPOTRACK is to query existing systems for what packages are installed from a given repo. To gather my EPEL package list, I ran these two commands on all of my application servers:

Parse the results however you want, and you’ve got the basis for your repotrack script. Repotrack doesn’t behave exactly like reposync, but it DOES get dependencies for packages, so it isn’t necessary to identify everything in advance. It also works with wildcards.

Synchronize the directories for the repositories.

The –newest-only option puts only the latest version of each package in the repos.

note: “repoid” must match a repo name in “/etc/yum{$}.repos.d/{$}.repo”