#14564: port -uR upgrade doesn't upgrade dependencies ------------------------------------------+--------------------------------- Reporter: waltman-macports@mawode.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: invalid | Keywords: ------------------------------------------+--------------------------------- Changes (by dluke@macports.org): * status: new => closed * resolution: => invalid Comment: -u can be used without -f, it's just not really useful unless you use it with -f. -u should be avoided in general though. It's better to do the upgrade and then uninstall (with -f) the newly inactive ports. -R will rebuild everything that depended on the new port, this is only actually necessary some of the time, but macports isn't yet smart enough to only do it if it's necessary. IIRC using -R with -f can cause multiple rebuilds which is annoying. To address your original questions: 1. No ports depend on specific versions of other ports. If you upgrade a library and its ABI changes anything that depended on that library will most likely have to be rebuilt (this is what -R is for). Frequently, though, library authors try to maintain ABI compatibility. For my personal usage, I use port -dvnf upgrade outdated and then manually fix things if necessary (or use -R if I know there is an ABI change). 2. aterm didn't get rebuilt because things stopped after the uninstall error 3. Without the actual output, it's difficult to determine why on your system the message was printed 6 times. The upgrade code isn't very long, though, so you could probably figure it out yourself if you were really curious. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14564#comment:3> MacPorts </projects/macports> Ports system for Mac OS