Upstream of dev-vcs/gitg has migrated to supporting GTK+ 3.x only. When do you plan to move GTK+ 3.x from the overlay to the main tree? In the mean time, could ikelos and I put gitg updates in the gnome overlay? Are there any rules to follow besides those known from the main tree?
If you have access to the overlay, feel free to add your ebuilds requiring gtk+:3 there, otherwise adding them to the tree masked with the rest of ebuilds requiring gtk+:3 is ok (rygel, tracker, ...). We will add it as soon as we've fixed a decent share of ebuilds across the tree that do not specify slot dependencies as requested weeks ago on the gentoo-dev ml. If you want to get an idea of how much work is left, you can either ask nirbheek for his pointers as he's been doing most of the work, or you can run one of the scripts of the overlay, such as slot_rindex2.py.
Once this list is empty, we can add gtk+:3 to the tree: http://dev.gentoo.org/~nirbheek/gnome/3.0/slotting/gtk+_rdeps.list
(In reply to comment #1) > If you have access to the overlay, feel free to add your ebuilds requiring > gtk+:3 there Okay, thanks. > We will add it as soon as we've fixed a decent share of ebuilds across the tree > that do not specify slot dependencies as requested weeks ago on the gentoo-dev > ml. > > If you want to get an idea of how much work is left, you can either ask > nirbheek for his pointers as he's been doing most of the work, or you can run > one of the scripts of the overlay, such as slot_rindex2.py. Thanks for these details. I'll join fixing if my time permits.
gtk+3 was added to the tree today. Themeing is still problematic on anything other than GNOME 3 — widgets aren't themed at all since the engine changed completely. Besides that, everything else should work perfectly well. Some apps still depend on >=x11-libs/gtk+-2, and they need to be fixed, so help in that regard is appreciated.
