Please add/fill bugs to the depend if any.
I think bugs 357831, 403093 and 403107 are about 0.9.x branch of compiz, which is not experimental(as i now) and that's why they should be here(maybe i am wrong?) because we are trying to return stable 0.8.x branch into main tree. Also, bug 357813 is not reproduced with my ebuilds(maybe somebody can do more complicated tests then just installation with different python versions?)
P.S. Naohiro Aota, i see, that you add x11-wm/compiz to main portage tree and unmask it. What's about all other ebuilds, needed for compiz, such as plugins etc?
(In reply to comment #1)
> P.S. Naohiro Aota, i see, that you add x11-wm/compiz to main portage tree
> and unmask it. What's about all other ebuilds, needed for compiz, such as
> plugins etc?
I'm willing to add them too. However, I have some real life works to be done for now. I'll restart ebuild works in a three days.
add me to a helper list if you want to make 1. I started doing a version bump on a little known package called gwibber. The new version pulls in a number of new deps including 3 or so compiz packages
As a quick note much newer versions of all the compiz packages are in the desktop effects overlay. Can these be brought over upon inspection? They're working well for me.
Naturally as I say that it now fails to compile for me. But it would be a handy starting point...
(In reply to comment #3)
> add me to a helper list if you want to make 1. I started doing a version
> bump on a little known package called gwibber. The new version pulls in a
> number of new deps including 3 or so compiz packages
I have working ebuilds for new compiz version in my overlay on github. You can use it for testing new gwibber version...
This tracker was created to fix issues with compiz 0.8 in main tree and compiz 0.9 in overlay. For now, critical issues are fixed, so i close this bug as FIXED. When compiz 0.9 will be ready for inclusion to main tree, i will file a new tracker bug.