On Fri, 2007-07-20 at 00:02 -0400, Eric Polino wrote: > > Someone mentioned just killing the USE flags and making them all hard > > dependencies, however. I really hope that's not done if additional > > dependencies are involved. > > I see your point, but how different would this be to any application > that requires dependencies and you can't change the fact that they > require them. For instance, any application that uses GTK+ requires > GTK+ and there's nothing you can do about it. I don't care how much > you strip down Firefox, you'll still need GTK+. The Pidgin team > "sells" their application as having all these protocols so they should > be there, at least out of the box.
Why is it configurable, at all, then? If the pidgin team wants these protocols enabled by everyone, why make them optional? I fully agree that the *defaults* should be sane, but if upstream doesn't want people turning these things off, why give people a switch? It's like putting out a big shiny red button that says "don't press me" then complaining when people press it. ;P Anyway, if nobody objects and nobody beats me to it, I'll add the USE flags for the common protocols to package.use in the profiles. Now, the real question is what should I enable? -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
