Thank you Mr. MacKinnon:<br><br><div class="gmail_quote">On Sun, Oct 25, 2009 at 11:05 PM, Alan McKinnon <span dir="ltr">&lt;<a href="mailto:alan.mckinnon@gmail.com">alan.mckinnon@gmail.com</a>&gt;</span> <br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

<div><div class="h5"><br>
<br>
</div></div>Did you try the most straightforward (albeit lengthy) approach:<br>
<br>
unmerge all of Qt<br>
emerge world and let portage figure out what it wants to put back<br>
<br></blockquote><div><br>How can I do this?  <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There is seldom a good reason to have Qt packages in world (dev packages<br>
excepted) and recent changes in the ebuild have caused lots of mutual<br>
blockers. When I first went through this, I saw that almost all qt-* packages<br>
would be rebuilt on my machines. It seemed easier to restart with a clean<br>
slate. I got a blocker notice which said I had to enable various flags, which<br>
I did and the merge completed flawlessly.<br>
<font color="#888888"><br></font></blockquote><div><br>I will try to uninstall all &quot;qt-*&quot;  packages.   I&#39;d like to uninstall KDE4 also.<br><br>Alan Davis<br></div> <br></div>