stale dependencies and portupgrade

[Vivek Khera]

I've been using portupgrade for a long time now.  Recently I've been  
noticing (though I'm sure it has been happening all along) that  
dependencies are not cleanly propagated to other ports.

Example:  p5-Expect used to depend on p5-IO-Stty which was removed  
from ports recently.  rt36 depends on p5-Expect, so got a transitive  
dependency to this dead port.  Upgrading p5-Expect using "portupgrade  
-Rr" took care of the direct dependency, but the upstream ports still  
had the registered dependency to p5-IO-Stty.  I had to force- 
uninstall that port then run "pkgdb -F" to remove that dependency.

Similarly, with a portupgrade of portupgrade itself, most of my  
machines lost the dependency to ruby18-bdb1 package.  The only way  
out of that was to do a delete of portupgrade and run a fresh make  
install in the port directory.

I suppose the bug is that I expected portupgrade -Rr to recompute the  
dependency lists of the upstream ports to take into account any  
changing dependencies of the updated port.

Do other port manager utilities take this type of change into  
account?  At this point, I'm not sure any of my dependencies are  
accurate on the complex ports like RT.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                MailerMailer, LLC     Rockville, MD
http://www.MailerMailer.com/                     +1-301-869-4449 x806