Since libnitofy and libnotify are available in the portage tree, gossip can take advantage of this. Also, there is no more need to fix omf.
Created attachment 83980 [details, diff] Ebuild correction proposal
I decided not to support these unstable APIs yet, given their 'in-flux' state it would probably only cause problems for users over time.
*** Bug 131410 has been marked as a duplicate of this bug. ***
Hi Foser, I know that libnotify and galago APIs are not in their *final* state, but as both packages are in the portage under ~keyword, and gossip is in the same state, I don't think that adding both flags will cause lot of problems (i'm using 0.10.2 and 0.11 without problems [~x86]). Rhythmbox and xchat-gnome are using them. If you still think that this patch to enable libnotify and galago isn't useful for now, at least look at the omf_fix part; it is not needed now.
Created attachment 88888 [details] gossip-0.11.1.ebuild Updated ebuild for gossip 0.11.1 with libnotify and galago support. No changes in the ebuild were needed to support 0.11.1 specifically, although I did change the libnotify dependency to check for >= 0.3.2 (as does the Gossip configure script).
Net-im is entering a joint maintainership of gossip with the gnome herd. I feel that this is a genuine change.
Your change is in the gossip 0.11.2 ebuild, which will be in the tree in under 2 hours. Committing it to CVS now. Thank you for your bug report :)
