On Tue, Jan 12, 2010 at 9:09 AM, inode0 <[email protected]> wrote: > On Tue, Jan 12, 2010 at 9:48 AM, Michael Stahnke <[email protected]> wrote:
> My understanding of EPEL's mission was that it would allow me to begin > with a RHEL + layered product box, configure EPEL, get additional > stuff without creating new problems. I think that is a wonderful > mission. I think that was one vision. The issue is that it is almost impossible in practicality to accomplish. Especially when some RH channels replace stuff that is in core (MRTG). It makes the job of EPEL a lot more of reacting to unknown forces and also makes it hard when say we have been putting cobbler or puppet in and then a previous version shows up on RHN. We can remove our version but its not going to fix the person who has the newer version and then never gets updates to what is in RHN. I will be making a list of all these sub-packages today.. will see what would need to be removed. > If this becomes I can begin with a box with anything I can get from > AP, configure EPEL, get additional stuff without creating new problems > I think we have a slightly less wonderful mission abstractly but > perhaps a more effective mission in the real world. > > John > > _______________________________________________ > epel-devel-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/epel-devel-list > -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
