source: trunk/base/doc/port-upgrade.1.txt

Last change on this file was 140804, checked in by raimue@…, 4 years ago

doc/doc-new: Clarify updating a single port may lead to errors, closes #48909

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 3.1 KB
Line 
1// vim: set et sw=4 ts=8 ft=asciidoc tw=80:
2port-upgrade(1)
3===============
4$Id: port-upgrade.1.txt 140804 2015-10-03 15:22:54Z raimue@macports.org $
5
6NAME
7----
8port-upgrade - Upgrade a port to the latest version
9
10SYNOPSIS
11--------
12[cmdsynopsis]
13*port* [*-vdqysbckpotf*] [*-D* 'portdir'] *upgrade*
14     [--enforce-variants] [--force] [--no-replace] [--no-rev-upgrade]
15     [['portname' | 'pseudo-portname' | 'port-expressions' | 'port-url']]
16     [+/-variant ...]
17
18DESCRIPTION
19-----------
20*port upgrade* will upgrade the given installed ports to the latest available
21version. To upgrade a port, MacPorts needs an updated port definition, which can
22be obtained using the man:port-selfupdate[1] command. You should regularly run
23*selfupdate* followed by *upgrade outdated* to make sure your system has the
24latest versions and bug fixes.
25
26When specifying variants during upgrade, the order of precedence is
27
28. variants specified on the command line
29. variants active in the latest installed version of the port
30. variants specified in man:variants.conf[5]
31
32In most cases, you should specify the *outdated* pseudo-port expression as
33argument to *port upgrade* to upgrade all ports where a newer version is
34available. This is the recommended upgrade method for end users.
35See man:port[1] for more information on pseudo-port expressions.
36Upgrading individual packages should only be performed by expert users who
37know what they are doing, since a mix of upgraded and non-upgraded packages
38can lead to various software errors.
39
40OPTIONS
41-------
42*--enforce-variants*::
43    Upgrade all given ports and their dependencies where the installed variants
44    do not match those requested on the command line, even if those ports aren't
45    outdated.
46
47*--force*::
48    Ignore circumstances that would normally cause ports to be skipped, such as
49    not being outdated.
50
51*--no-replace*::
52    Do not automatically install ports that replace a now-obsolete port you have
53    installed.
54
55*--no-rev-upgrade*::
56    Do not run rev-upgrade after upgrading. See man:port-rev-upgrade[1] for more
57    information.
58
59
60include::global-flags.txt[]
61
62*-f*::
63    Upgrade a port, even if it is not outdated.
64
65*-n*::
66    Only upgrade the given ports and avoid upgrading their dependencies. This
67    flag may be useful when combined with *--enforce-variants*.
68    +
69    WARNING: Ports expect their dependencies to always be at the latest version,
70    which is why MacPorts upgrades dependencies first. Do not specify this flag
71    if you don't know what you are doing.
72
73*-p*::
74    Keep going and attempt to upgrade the next port when a port fails to build.
75    +
76    WARNING: This option is harmful to *upgrade* and should be avoided at all
77    cost. Often, MacPorts ports are only upgraded to rebuild them against
78    updated dependencies. Specifying this flag will cause a spurious rebuild if
79    a dependency of a port fails to build and leave your system in a broken
80    state once the dependent port is fixed.
81
82SEE ALSO
83--------
84man:port[1], man:port-uninstall[1], man:port-info[1], man:port-variants[1],
85man:port-rev-upgrade[1], man:port-setrequested[1], man:variants.conf[5]
86
87AUTHORS
88-------
89 (C) 2015 The MacPorts Project
90 Clemens Lang <cal@macports.org>
Note: See TracBrowser for help on using the repository browser.