On Apr 7, 2007, at 8:06 PM, Paul Beard wrote:
On Apr 7, 2007, at 4:49 PM, Ryan Schmidt wrote:
If some other ports depend on the port you're trying to upgrade, then port will complain, unless you use the force option. I wish it weren't that way -- I wish port were smart enough to figure out that you are installing an upgrade to the port, not merely uninstalling the port, therefore it should allow the (momentary) uninstallation. However, port is not that smart.
It seems confusing to have word commands (install/uninstall) along with single-letter arguments, in that case. port upgrade <some port> should (says a guy who can't code) just upgrade the port, upgrade any dependences (by which I mean things it depends on) if needed, and clean up after itself.
That's what it does (sort of). It's just that most of the time, it's faster do do: port -unf upgrade outdated port upgrade foo will attempt to upgrade foo and anything else in it's dependency tree that needs upgrading. It's just that it decides to play it safe and not uninstall/deactivate anything that something else is using unless you force it to (so upgrade won't break existing installs).
Dependent ports, things that rely on the port you upgrade, do not get upgraded automagically.
That's correct, because in the 'normal' case it's not what you want to have happen. You can request it to happen with -R.
So, theoretically, if you upgrade gettext, you have to upgrade libiconv and expat. But if you upgrade expat, gettext is not upgraded.
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+