The plan is for EPEL packages to get updates as long as the corresponding RHEL release is supported. That is seven years after the initial release according to the current errata support policy. The only way to be sure is to do it yourself, which is coincidentally the reason EPEL was started in the first place. Software packages in EPEL are maintained on a voluntary basis. If you to want ensure that the packages you want remain available, get involved directly in the EPEL effort.

You have to follow the same process as Fedora except that you can request an EPEL branch, tag, and build.

Refer to the EPEL package maintenance and updates policy for all the details -- for a short overview, read the digest: The goal is to have packages in EPEL that enhances the Enterprise Linux distributions the packages were build against without disturbing or replacing packages from that distribution. The packages in the repository should, if possible, be maintained in similar ways to the Enterprise Packages they were built against.

There are repository rpm packages for RHEL4 and RHEL5. The repository package installs the repo details on your local system for yum or up2date to use. Then you can install packages with your usual method, and the EPEL repository is included. su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-2.noarch.rpm' ... su -c 'yum -y install foo'

EPEL (Extra Packages for Enterprise Linux) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages that complement the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, such as CentOS and Scientific Linux. part of the Fedora packaging community, EPEL packages are 100% free/libre open source software (FLOSS).

Packages are freely available and it is an explicit goal of the project to make sure they are usable for RHEL-based distributions such as CentOS and Scientific Linux.

Packages are peer reviewed against extensive packaging guidelines before being imported into the repository. Only updates that fix important bugs get pushed to the stable repository directly. Other updates hit a testing repository first and get released as an EPEL scheduled update in parallel with the EL scheduled updates. Packages often are tested in Fedora, too. The Fedora Packaging Guidelines and QA team back up all these efforts, helping to avoid errors.

The plan is to have one primary maintainer per packages who is responsible for making certain that the package enhancements applied to one tree (for example, EL4) find their way into the other trees (for example, Fedora devel). This maintainer decides what makes sense to apply for the package in general. New EL branches for new EL releases are normally be created from the associated Fedora branch on which the EL release is based.

EPEL project provides add-on packages for Red Hat Enterprise Linux 5.x and 4.x releases and compatible derivatives. Packages for Red Hat Enterprise Linux 3 and 2.1 are not provided since they are under maintenance phase following the errata support policy from Red Hat and packages sourced from Fedora is unlikely to build properly against the older version of packages available in these releases making it very difficult to maintain properly.

Croquet-Updates-mpm.1.mcz - is not needed by most people. It is just there for those who will create changesets for the update stream, but we almost never use the update stream, and only a few people create changesets for it, so ignore this. Only packages from the four standard repositories, Homebase, Tweak, Hedgehog, and Contributions, should be saved in your normal image.

rpm -qp foo-0.1-5.el5.i386.rpm --qf '%{NAME}-%{VERSION}-%{RELEASE} %{VENDOR}\n' foo-0.1-5.el5 Fedora Project $ rpm -qp foo-0.1-5.el5.i386.rpm --qf '%{NAME}-%{VERSION}-%{RELEASE} %{DISTRIBUTION}\n' foo-0.1-5.el5 Extras Packages for Enterprise Linux $ rpm -qp foo-0.1-5.el5.i386.rpm --qf '%{NAME}-%{VERSION}-%{RELEASE} %{SIGGPG}\n' foo-0.1-5.el5 883f030500468e3e4e119cc036217521f611025863009f5fe424c6fe4bc81a57f45722e465e71381dda2f6009f7c08e1743794b5b9a5a4cd149081092801a5d935

Anyone interested. If you are using RHEL or compatible spin off's and if you have the required skills for maintaining packages or are willing to learn, you are welcome to contribute.

Choose from our simple 0.05 per minute/$5.95 monthly fee package or our unlimited 0.07 per minute package with no monthly fee.

The Ultimate Resale packages will be added to as time goes by, at the moment it will take many, many hours. Factors concerning the speed of your Internet connection can vary the download times of individual products. But you can download them at your leisure or as you require them, so speed is not the issue.

It can take up to 48 hours after the hosting package is setup or after the domain has been transferred for the Web Site to be viewable on the internet

For most shipping locations, the packages arrive in 10-14 days. However, in some instances, it can take up to a month or more for the care package to actually be delivered to your Marine.

The containers spend about seven to ten days in transit. Usually we can deliver regular mail in about fifteen to twenty days.

The shelf life of our products range from 8 to 15 months, and is indicated by the package. Generally the single serves are 8 months, the boxes are 10 – 12 months, the stand up bags are 12 months, and the cans are 15 months. The recommended shelf life indicates a period when the product has optimal flavor and freshness. Product beyond the recommended shelf life may experience slight changes in flavor, color and nutritional value.

Most packages are sent by Royal Mail on the same day that you ordered as long as it was before 4.00pm. Large packages are either sent by courier, suing Parcelforce or by Royal Mail 'Signed For' service.

Catalyst uses Portage for all of the building work, so all that you have to do is regenerate your Portage snapshot and rebuild your GRP/stages/LiveCD. Portage will follow all of its normal rules for deciding which packages to update.

It'll show up in the news. And if you demand I update, or contact me only to tell me to update, it won't exactly help much. An inquiry as to how I'm doing or feeling would be great, though.

You should receive a reply within a week. In that reply, you will be either told that it is done, asked for more information, or told the time frame for processing. The Drachenwald OP allows the use of multiple names. If you have an alternate name, or received awards under different names, we can track those multiple names and link them all to your record. Be sure to tell us about any alternate names you have!

After the first registration, as soon as you receive the confirmation via email your data will be in our database. Then if you need you can login to the Domain Manager to update your data. Once you modify your domain information it is instantly updated on our server. It may take up to 24 hours for root servers of InterNIC to reflect the updates. Using Domain Manager, change your name servers to the name servers of your existing web page's hosting company.

It will probably take 2-3 days after confirmation for the whois database to be updated. This is beyond our control.

It depends upon the editor of your category. But it will be updated in 2 weeks of time. If you are asking for changing of title or description that is not under the guidelines of this directory we can reject your updating.

A large number of contributors and users of Fedora and Enterprise Linux want to work within Fedora to provide these packages. The Fedora Project is a user of EPEL packages within the Fedora infrastructure itself. The Fedora Project is in a position to know the pain of not having a desired piece of software included in the RHEL distribution, and also a unique position to do something about it.

There were a lot of long discussions in the months of EPEL about using repotags or not. Lots of people from inside and outside of Fedora and EPEL as well as maintainers from other repositories participated in those discussions. No real agreement could be found if the benefits outweigh the disadvantages -- part of the problem was that people sometimes not even could agree what benefits or a disadvantages repotags have (or if there are any).