Summary: | net-im/pidgin-2.6.4-r1 doesn't enable xscreensaver extension by default | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | peng shao <shallpion> |
Component: | Current packages | Assignee: | Gentoo Net-im project <net-im> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | notordoktor |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
peng shao
2010-01-10 22:01:29 UTC
I couldn't agree more. Completely missed that when reviewing these changes. Made it the default now. Fixed (In reply to comment #1) > I couldn't agree more. Completely missed that when reviewing these changes. > Made it the default now. Fixed > Thanks a lot :) Have a nice day. I disagree. xscreensaver is global flag and as such should not be IUSE default enabled. Look, one may say that without gtk pidgin is not pidgin, but well, having gtk enabled with IUSE-default is stupid idea. Same goes for any global USE flag. (In reply to comment #3) > I disagree. xscreensaver is global flag and as such should not be IUSE default > enabled. Look, one may say that without gtk pidgin is not pidgin, but well, > having gtk enabled with IUSE-default is stupid idea. Same goes for any global > USE flag. OK, so when you have one package with (local) USE=foo, then it's OK. Say after one year, 10 completely unrelated packages with IUSE=foo get collected in the tree, someone makes the flag global and then the IUSE="+foo" becomes invalid? Uh, how does this make any sense and where's such policy written? Maintainer should be free to choose whatever flag(s) to be enabled by IUSE-defaults, per norm those would match upstream defaults or whatever sane default to prevent in-flow of stupid "bugs", like "ooooh WTH, I have no GUI". And wrt your gtk example, that'd be yet another that should be enabled by default here. ok let's keep this issue closed for now. |