On 11.12.2007 15:35, Jesse Keating wrote: > On Tue, 11 Dec 2007 14:28:14 +0100 > Thorsten Leemhuis <[EMAIL PROTECTED]> wrote: > >> The proper answer IMHO is to do what we planed from the start, but >> never realized: create per dist dirs like epel/5.1. When 5.2 ships to >> a "cp -al 5.1 5.2", update the builders and ship all newly build >> packages in the 5.2 dir. Once CentOS 5.2 is out delete the 5.1 dir. >> The only problem: we'd need to push security updates to both the 5.1 >> and 5.2 dir during the delta where CentOS catches up. >> BTW, we will likely cause problems for RHEL/RHN customers in any case >> in rare situations when RH ships updates because we don't get new RHEL >> update releases in advance -- thus we might now and then need a day or >> two to catch up in case something from EPEL needs to be build against >> a new updated package (firefox, pidgin, ...) from RHEL. > This is where RHEL z-stream updates will come into play.
That's another issue. But there is one thing about them that I never understood: when does RH do them? Only for selected releases? And BTW: I'm wondering if EPEL should just ignore them for now; sure, would be nice to support them, but I suspect we don't have the manpower nor the tools to properly support them right now. Yeah, that sucks, but there are bigger problems to solve first IMHO. > Please ping me for the next EPEL meeting as I'd like to discuss this > during the meeting. Sure, will do (next meeting will be next weeks Wednesday at 18:00 UTC, in case it matters), but maybe you can find the time to explain your thoughts first here on the list first over the next few days -- having the major thoughts shared before discussing a issue on IRC IMHO makes everything a whole lot easier and quicker. And mailing lists have no timezone problems ;-) CU knurd _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
