<h3>Via RPM<aclass="headerlink"href="#via-rpm"title="Permalink to this headline">¶</a></h3>
<h3>Via RPM<aclass="headerlink"href="#via-rpm"title="Permalink to this headline">¶</a></h3>
<p>RPMs for the last Ansible release are available for <aclass="reference external"href="http://fedoraproject.org/wiki/EPEL">EPEL</a> 6 and currently supported
<p>RPMs for the last Ansible release are available for <aclass="reference external"href="http://fedoraproject.org/wiki/EPEL">EPEL</a> 6 and currently supported
Fedora distributions.</p>
Fedora distributions. Ansible itself can manage earlier operating systems that contain python 2.4 or higher.</p>
<blockquote>
<blockquote>
<div># install the epel-release RPM if needed on CentOS, RHEL, or Scientific Linux
<div># install the epel-release RPM if needed on CentOS, RHEL, or Scientific Linux
<p>Note that if you are tracking the upstream source (i.e. git), the RPM revision will not be
bumped with every source code change. To get around this, you can use
<ttclass="docutils literal"><spanclass="pre">rpm</span><spanclass="pre">-Uvh</span></tt> with <ttclass="docutils literal"><spanclass="pre">--force</span></tt> when RPM tells you the package is still at the