Compiz 0.6.2 now requires >=x11-libs/libwnck-2.20.1 In turn, libwnck wants a newer gtk+, etc. While I realise that Compiz is still marked as unstable (and might require unstable libraries), has there been a reason for upping the dependencies without bumping the Compiz version? Yeah, I'm just unkeen to run an unstable gtk+... :) - can you provide ebuilds that *don't* require newer libs?
That has been fixed on 24th of Oct. Then did you do your last sync?.. Here is part from the ebuild: >=x11-libs/libwnck-2.20.1
sorry, I miss read it. The the very first compiz dump didn't required that version of libwnck and it has been added afther 24th only. I don't know the real reason for that.
It would be nice to know why the dependencies have changed. I changed the ebuild for me and compiz-0.6.2 runs very well with libwnck-2.18.3.
I had a request on irc that compiz has problems with old libwnck-versions, but maybe I've raised it a bit too high. I've lowered it now to .18, as long as no further bugs appear, we can leave it there. But let me note that it's probably not the best idea running a "stable" system with something like compiz.
Thanks Hanno for your work on compiz ebuild. When you upgraded the package requirements on 24th of October, beside libwnck you also upgraded libxml2 from 2.6.28 to 2.6.30 libxml2 2.6.30 is marked unstable. While I understand your reasoning that "it's probably not the best idea running a 'stable' system with something like compiz", on 24th of October I was able to run compiz on a stable system (just by keywording compiz related ebuilds) Now, in order to run compiz, I have to make my system more unstable, because of this libxml2 2.6.30. Is it really required? Can't you just leave it at >=2.6.28? It worked perfectly for me on 24th :) thanks, Dan.
