I tend to agree with Mike and several of the previous comments in this thread.
EPEL was designed to supplement EL with packages not included in the base. It has been, and will continue to do this. If the package is updating too frequently, the solution is simple, don't update. (disable automatic yum, or up2date or whatever). Create a release strategy for your needs. The repository and upgrade strategy are not (and should not) be one in the same. If it's not updating often enough, you are welcome to uses other repos, or supplement with your own updates. I tend to think that currently, the Fedora Project and contributors would not be able to sustain a quality-driven branch for unstable, or 5.1 vs 5.2 etc and so on. I still think that EPEL is much better than me having to hand pick every RPM from Fedora SRPMS and recompile them by hand, store them in my own repositories and then watch as incompatibilities crop up. Keep in mind that EPEL's goal is to make high-quality, fedora approved, packages available. How you use them is up to you. I also gave a talk on managing updates at the Red Hat Summit, if you want to check it out, please do so. http://stahnma.fedorapeople.org/summit/updates.odp stahnma _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
