The gaim executable is linked against: libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so.0 (0x410d3000) So, I think startup-notification should be a dependancy in the GAIM ebuild? A friend set up a basic system (2004.0 GRP) and merged the prebuilt gaim binary, and was unable to start it until I asked him to merge this.
I'm using gaim just fine without startup-notification installed. Gaim automatically uses startup-notification if it finds it. Your friend had that link show up in his ldd output before installing startup-notification? Sounds to me like he had some sort of b0rked startup-notification setup lying about.
Apologies for not looking closer into that first, I just assumed that it was a non-optional dependency. In that case, the problem is a GRP bug - the gaim binary was obviously built on a system with startup-notification installed, and will therefore not run when unpacked onto a system not running startup-notification.
Hmmm yeah that would make sense. Not sure how we'll fix that. I'll ask releng, perhaps I'll have to dep on startup-notification after all just to be safe.
Perhaps you could add the --disable-startup-notification flag to the ./configure call, when the livecd use flag is set.
Just an FYI that I'm going to add startup-notification as a DEPEND full-time in gaim.
