portmanager upgrade question

[Bart Silverstrim]

Is there a way to force a rebuild with new dependencies when you get 
errors like:
******
OLD ethereal-0.10.11_1 built with old dependency net-snmp-5.2.1_2, 
current dependency is net-snmp-5.2.1.2
OLD gtk-2.6.8 built with old dependency libxml2-2.6.19, current 
dependency is libxml2-2.6.20
OLD shared-mime-info-0.16_1 built with old dependency libxml2-2.6.19, 
current dependency is libxml2-2.6.20
------------------------------------------------------------------------
status report finished
========================================================================
percentDone-=>0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=>4 / 
TOTAL_outOfDatePortsDb-=>4 ) )
upgrade 0.2.9_4 info: ignoring ettercap-0.6.b_2,1, reason: failed 
during (2) make
checkForOldDepencies 0.2.9_4 skip: ethereal-0.10.11_1 has a dependency 
shared-mime-info-0.16_1 that needs to be updated first
checkForOldDepencies 0.2.9_4 skip: gtk-2.6.8 has a dependency 
shared-mime-info-0.16_1 that needs to be updated first
upgrade 0.2.9_4 info: ignoring shared-mime-info-0.16_1, reason: failed 
during (2) make
------------------------------------------------------------------------
update of ports collection complete with either some errors, ignored 
ports or both
========================================================================
*******
at the end of an upgrade cycle, like a recursive rebuild?  Or do other 
tools have to be used outside of portmanager?

Thanks,
-Bart