dev-libs/libappindicator doesn't install the python bindings, which are provided with the archive. To have an USE flag for that would be great. Reproducible: Always Steps to Reproduce: 1. emerge -a1 libappindicator 2. 3. Actual Results: Calculating dependencies... done! [ebuild R ] dev-libs/libappindicator-12.10.0:3 USE="introspection" 0 kB Expected Results: Calculating dependencies... done! [ebuild R ] dev-libs/libappindicator-12.10.0:3 USE="introspection python" 0 kB It is also the mono and vala bindings that can be useful for other peoples. Nut my main concern is the python bindings which are needed by Screencastor to have the tray icon. http://hizo.fr/linux/screencastor/ http://www.linuxcore.fr/2012/06/screencastor
Yes, they are purposely skipped because :3 is for GTK+-3.x and the Python bindings are for GTK+-2.x We don't have the manpower to maintain Unity in Portage, and have selectively chosen to install only GTK+-3.x based minimal set of Unity libraries Thus, yes, it's correctly not installing the PyGTK-2 bindings
As in, you can create libappindicator at SLOT="2" for GTK+-2.x or use the user maintained Unity overlay
And mono bindings are not installed because MONO is broken in Portage, and we are waiting for bug 458812 Can't remember out from memory what the vala status was, but every binding was reviewed at the time of packaging
