<div dir="ltr">Even if the old ports that are dependencies of the old port still exist, the upgraded port with the new dependencies downloads and builds the new dependencies before it upgrades itself. Even if this process accumulates useless or redundant ports over time, it should not affect the build of the newer ports, right? </div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 19, 2014 at 2:43 PM, Brandon Allbery <span dir="ltr"><<a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class=""><div class="gmail_quote">On Sun, Oct 19, 2014 at 2:42 PM, Carlo Tambuatco <span dir="ltr"><<a href="mailto:oraclmaster@gmail.com" target="_blank">oraclmaster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">When you upgrade a port, everything it depends on gets updated first, right? What doesn't get upgraded should not affect what does get upgraded during the configure/build/install/activate phase, right? So how is using -u different from uninstalling everything and reinstalling everything again?</div></blockquote></div><br></span>When the new version of a port has different dependencies from the old version.<span class=""><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</span></div></div>
</blockquote></div><br></div>