On 03/10/2003 at 10:57:40(-0700), C. Brewer used 1.5K just to say:
> I hear what you're saying, but I guess I wasn't particularly clear.
> Basically, you have the fix for it, and it's nice, and it works. However,
> what I was trying to get at is this- rather than write an eclass, why not
> fix the package itself and kick it back to Slack?

This idea was also in one of the comments of the bug.

http://bugs.gentoo.org/show_bug.cgi?id=23249#c13

(second comment from the bottom for now)

> Sure, there's a chance
> they won't care to change it, and the eclass would be necessary, but now
> we're at a point with everyone fixing everything, the tree is getting to
> carry almost the amount of patches as it does packages. So I apologize if
> I'm unclear or frustrated, but it feels as if rather than sharpen an old
> knife to do the work, we just make a new knife. I realize that's not the
> intent of anyone, but if the fixes and work arounds don't get back
> upstream, how long until patches and fixes do outweigh the packages?
> (I'm up to ~60k files from the ~20k when I first installed!)

-- 
/\   Georgi Georgiev   /\ A real friend isn't someone you use once and /\
\/    chutz@gg3.net    \/ then throw away. A real friend is someone    \/
/\  +81(90)6266-1163   /\ you can use over and over again.             /\