If a meanwhile (library for connecting to Lotus Sametime) user is upgrading from gaim-1.x to gaim-2.0, he/she probably has gaim-meanwhile installed, which provides meanwhile connectivity in gaim-1.x. In 2.0, meanwhile support is built in, and does not require a plugin. But gaim-2.0.0_beta3.ebuild does NOT check whether it is installed! When gaim-meanwhile IS installed, and gaim-2.0.0 is installed over gaim-1.x, gaim will segfault immediately upon startup (or specifically, while loading a meanwhile account or trying to connect to the meanwhile server). No useful information is ever given until you perform a backtrace, which would point one in the direction of meanwhile. While trying to debug this, I started recompiling lib-meanwhile and gaim-meanwhile with the debug USE flag. gaim-meanwhile failed, stating that it requires a gaim version >= 1.2.0, but < 2.0.0. This reminded me that gaim-2.0.0 has meanwhile support built in. I uninstalled gaim-meanwhile and the segfaults went away. The point here is that the gaim-2.0.0 ebuild should block when gaim-meanwhile is installed (note lib-meanwhile is still required). This would save a lot of other people many headaches.
Will test this, and add appropriate info into the ebuild for 2.0.0beta#
Adjusted both the gaim-meanwhile and gaim beta ebuild appropriately.
