Well if pertty got a use flag the agreed xgl should too! No side effects with patch though.

I compiled all the Xgl stuff, got it mostly working... however, I found the rubber band effect gone and the desktop Icons had the text off center from the Icon.

Any ideas?

EDIT:

I got it working again, however I don't know if it's related to the change to the ebuild I made or not for kdelibs + xgl..._________________If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

The patch just adds a Kicker Applet for Xgl stuff, so probably not related... But with the amount of irratic behaviour I've seen over the last couple of days from the experimental -bdirect boxes anythings possible..._________________Gentoo's Portage: Any ideas for reform?

anyone having problems using the wiki fuction in amarok while using these ebuilds? im usiong amarok 1.4 beta and wiki says "cannot fetch artist information can't connect to server" also have problems with superkaramba saying it cant find the file for the newest additions i cant quote the error atm... odd errors that seem to be possibly linked to konqueror???

So far only the konqueror ebuild needed the kurllabel patch removed. (changes in KDE now)
I will post if others need changes also.

That is awesome.

Let me know what works, and I'll upgrade to 3.5.2.

Thanks.

EDIT:

I have copied the ebuilds for 3.5.2 over to my overlay and added the perty patch to each. I'm in he process of building as well. Hopefully it goes well._________________If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

I finished the patches with an added treat. I finally fixed the konqueror patches so this means that the new sidebar thing is back and other konqui goodness. Also, added features to the other patches. To see what I mean, go to the control panel and then styles configuration and you should see some rubberband options. This means that these patches depend on pertty patch for QT, so don't forget to set that use flag. Also, you NEED to have XRENDER options for the rubberband to show up at all. It is not if def'ed so it will not be used unless your xorg.conf file is correct. See the first post on how to use the new sidebar thing and for the RENDER options I mention.

I am working on making the patch more gcc 4.1 friendly, and all bugs are suppose to be posted here. In the meantime, you can set up a workaround by adding -fpermissive to your CXXFLAGS. You can add it to your bashrc file in /etc/portage/bashrc. I will past the contents of mine so you can use it as an example. This will allow you to you have only -fpermissive on kdesktop. It installs just fine with this flag.

I know this is a workaround, but a more gcc 4.1 friendly solution is being sought after. Let me know of any other troubles. If there are, can you add a line to your bashrc with -fpermissive to see if that helps? Thanks

I am working on making the patch more gcc 4.1 friendly, and all bugs are suppose to be posted here. In the meantime, you can set up a workaround by adding -fpermissive to your CXXFLAGS. You can add it to your bashrc file in /etc/portage/bashrc. I will past the contents of mine so you can use it as an example. This will allow you to you have only -fpermissive on kdesktop. It installs just fine with this flag.

I know this is a workaround, but a more gcc 4.1 friendly solution is being sought after. Let me know of any other troubles. If there are, can you add a line to your bashrc with -fpermissive to see if that helps? Thanks

everyone says file bugs file bugs. blah blah! i say no i cant im using unstasble "who cares file anyways" so i flipping file the bug and i get this reply

I can understand your confusion there. You are only suppose to file bugs in bugs.g.o for stuff that is in the original portage tree. For things outside the portage tree, like these patches, you are suppose to file bugs in the thread that the program is talked about in, like this thread here. So, no worries.

Glad that workaround fixed. I need to go over the code some more this weekend to see if I can make it gcc4.1 compliant. ^^

I am working on making the patch more gcc 4.1 friendly, and all bugs are suppose to be posted here. In the meantime, you can set up a workaround by adding -fpermissive to your CXXFLAGS. You can add it to your bashrc file in /etc/portage/bashrc. I will past the contents of mine so you can use it as an example. This will allow you to you have only -fpermissive on kdesktop. It installs just fine with this flag.

I know this is a workaround, but a more gcc 4.1 friendly solution is being sought after. Let me know of any other troubles. If there are, can you add a line to your bashrc with -fpermissive to see if that helps? Thanks

just add -fpermissive to your CXXFLAGS and it compiles. But, yeah, I need to fix it for real. -fpermissive is more of a hack. But it works and is stable. _________________Nothing to read in this sig. Move along.