On Nov 30, 2008, at 23:46, Neil wrote:
On 1 Dec 2008, at 00:39, Ryan Schmidt wrote:
On Nov 30, 2008, at 15:17, MacPorts wrote:
`sudo port upgrade outdated`
-(you can add the `-v` flag following "port" in the above command
if you'd like to watch the compiler output).
+To upgrade all outdated ports and their dependencies:
+
+`sudo port upgrade -R outdated`
+
+(You can add the "`-v`" flag following "`port`" in the above
commands if you'd like to watch the compiler output.)
Do we really want to advise users, in the quick-start guide, to
use the -R option, which, according to multiple reports, doesn't
work so great?
I didn't know. If it doesn't work well, you could take it out; or
perhaps you might simply consider putting a disclaimer on it. I
didn't find it anywhere else in the documentation except for man
pages, and I thought it could also be useful.
Then again, how often does an update of a port induce a new
dependency? (Since existing dependencies should be caught up in
`sudo port upgrade outdated`...)
"port upgrade -R foo" also upgrades dependents (ports that depend on
foo), not dependencies (ports that foo depends on); dependencies are
always upgraded unless you use the "-n" flag.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
