Pidgin ebuild currently requires startup-notification and Xscrnsaver when compiling gtk frontend. It would be useful to allow building a "lighter" client without these. Reproducible: Always Steps to Reproduce: 1. USE="gtk" emerge pidgin Actual Results: startup-notification and XscrnSaver are installed Expected Results: Install pidgin without the startup-notification and XscnSaver support
Created attachment 206171 [details, diff] Patch to add USE flags for startup-notification and screensaver against 2.6.2 ebuild
Why? Any half-decent X implementation, from, you know, the last 20 years, has the xscreensaver extension. I see no valid reason to disable it. And well startup-notification is just 10 years old, not 20, but its almost no code. Not having it will not in any way make pidgin lighter.
(In reply to comment #2) Hi Olivier. I didn't mean to imply that either of the two libraries is malfunctioning or is untested; however neither one is providing features I'm actually utilizing. On a system with a desktop environment without startup notification support and with pidgin used for presence-less protocols, hard dependency on these libraries just adds two extra packages to look after. With the two features enabled by default is there any reason not to allow an option to omit them? Perhaps a "minimal" option, similar to that used in some packages can be added instead?
I agree with Lev: Gentoo is all about choice. mammuth packages like xulrunner have this use-flag, so why don't add it to pidgin too? The patch proposed it's really trivial and should be risk free, please reconsider your decisione and apply it. it's really weird that I'm forced to have startup-notification when upstream allow me to get rid of it.
