Yum broken = no testing

[Ralf Corsepius]

On Fri, 2004-11-26 at 02:02 -0500, seth vidal wrote:
> > Well...  it'd be much easier for a user running the current python to 
> > get a new yum RPM to be able to fix their system than to go through the 
> > dependency fun that is upgrading python when something like yum is 
> > "busted".  I am OK with this not going into the upstream yum package, 
> > but it might be worth adding to our packages for the time being....
> 
> so by that argument, if gtk had an api break then mozilla should work
> around it, rather than making the fix occur in gtk?
Yes. That's how things work in real world. 

As a developer you spend a significant time to work around bugs, API
changes and things which don't behave as you expect them to do.

Ralf