(You will probably have to retitle this Jakub :) ). First, a real (minor) bug before I go off on a mini-rant: The ebuild has (line 62 in 2.0.2): DYNAMIC_PRPLS="irc,jabber,oscar,yahoo,zephyr,simple,msn" But later we see: if use zephyr; then DYNAMIC_PRPLS="${DYNAMIC_PRPLS},zephyr" <whining> I have to say that I just don't understand the recent changes to this ebuild. I always saw the ability to leave out things I don't want as one of Gentoo's biggest strengths. Now, it seems that support for MSN has become mandatory (even though it worked fine before as a USE flag). Also, with the removal of the ssl USE flag, I have to build encryption into this whether I want to or not (again a perfectly working option via a USE flag before). This seems especially bizarre considering the change not too long ago where the gtk interface (which almost everyone certainly wants) doesn't get built without the gtk USE flag set. </whining> Back to one more USE flag problem (with one last complaint thrown in for good measure :) ). The crypt USE flag used to pull in pidgin-encryption (gaim-encryption then). This seems like reasonable behavior to me. The crypt USE flag doesn't even get used now (in 2.0.2). I believe it should again make pidgin-encryption a dependency.
Read the other bug and the huge thread on gentoo-dev ML. http://archives.gentoo.org/gentoo-dev/msg_147071.xml *** This bug has been marked as a duplicate of bug 186302 ***
(In reply to comment #1) > Read the other bug and the huge thread on gentoo-dev ML. > > http://archives.gentoo.org/gentoo-dev/msg_147071.xml > > *** This bug has been marked as a duplicate of bug 186302 *** Thanks for the list link. I didn't know that Gentoo received a request from above to include all the protocols. At least I could see (unlike those other clueless guys) that the change removed the option of not building msn support (which some might not want just for philisophical reasons :) ). I don't know if I agree with that decision, but at least I see some justification for it. Another ebuild gets added to my /usr/local/portage overlay. Sigh. I also don't agree with your decision to classify this bug as a duplicate. Aside from griping about the msn USE flag change, I pointed out that the crypt USE flag doesn't get used at all, and that zephyr gets built even with -zephyr, both of which should get fixed regardless.
Both bugs still exist even in the 2.1.0 ebuild Zephyr gets build by default, then later gets tested for and added (again) to the list of protocols to build. The ebuilds have a "crypt" USE flag that serves no purpose (never tested for).
zephyr shouldn't have been in the default, thanks for the notice
