Mock for EPEL4 with broken deps for ages

Stephen John Smoogen smooge at gmail.com
Thu Aug 12 18:31:59 UTC 2010


On Thu, Aug 12, 2010 at 12:20, Kevin Fenzi <kevin at scrye.com> wrote:
> On Tue, 10 Aug 2010 23:53:28 +0200
> Michael Schwendt <mschwendt at gmail.com> wrote:
>
>> On Tue, 10 Aug 2010 10:13:52 -0600, Stephen wrote:
>> > 1) We should  remove the FAQ documents?
>>
>> Seriously?
>>
>> There's a lot of "talk" in those FAQs, which doesn't match reality.
>> I'd favour a more honest/self-critical view of what EPEL is able to
>> deliver today … as opposed to what it could deliver if it had enough
>> volunteers to contribute.
>
> Yeah, it would be great to re-do/re-work the wiki pages.
>
> Would someone be willing to step up to do that?

Sounds like a SouthWest FAD to me :). Though a trip to Europe to meet
Michael would be interesting.

>> > 2) Would you like to be the EPEL-EL4 Tsar to deal with these issues?
>>
>> At present, you could not even tell _how_ "to deal with these issues".
>> I've found only one. How many others are there? (e.g. run-time issues)
>>
>> One thing for sure, it wouldn't be much fun to have one group bring
>> a package into EPEL and see how they drop the ball long before dist
>>>



-- 
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines




More information about the epel-devel-list mailing list