source: trunk/base/doc/port-selfupdate.1.txt @ 134980

Last change on this file since 134980 was 123948, checked in by cal@…, 5 years ago

base: unify formatting in manpages

  • all options are printed in bold
  • 'Portfile' is always underlined
  • fix list in port-lint.1
  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 3.7 KB
Line 
1// vim: set et sw=4 ts=8 ft=asciidoc tw=80:
2port-selfupdate(1)
3==================
4$Id: port-selfupdate.1.txt 123948 2014-08-16 13:45:03Z cal@macports.org $
5
6NAME
7----
8port-selfupdate - Upgrade MacPorts itself and update the port definition files.
9
10SYNOPSIS
11--------
12[cmdsynopsis]
13*port* [*-qvdf*] *selfupdate* [--nosync]
14
15DESCRIPTION
16-----------
17*port selfupdate* checks for new releases of MacPorts and upgrades it when
18necessary. *selfupdate* also updates the local port definitions (the so-called
19ports tree) to the latest state so you have the latest versions of ports
20available. This part of the operation corresponds to man:port-sync[1].
21
22You should regularly run *selfupdate* to update your local port definitions.
23Running *selfupdate* is required to get updated software with bug fixes and new
24features.
25
26OPTIONS
27-------
28
29*--nosync*::
30    Only check for updates - and install if available - for MacPorts itself. Do
31    not update the ports tree.
32
33include::global-flags.txt[]
34
35*-q*::
36    Supress status output, be as silent as possible.
37
38*-f*::
39    Do not check whether the downloaded MacPorts version is newer than the
40    currently installed one, but always rebuild and reinstall MacPorts.
41    +
42    You can use this to downgrade from a beta or development version to the
43    latest release. Note that there is no guarantee that there have not been
44    made incompatible and irreversible changes to MacPorts' internal data
45    structures, making a downgrade impossible.
46
47EXAMPLES
48--------
49When no new versions are available, *selfupdate* looks like this:
50
51[subs="verbatim,attributes"]
52----
53$ sudo port selfupdate
54---> Updating MacPorts base sources using rsync
55MacPorts base version {manversion} installed,
56MacPorts base version {manversion} downloaded.
57---> Updating the ports tree
58---> MacPorts base is already the latest version
59----
60
61If *selfupdate* detects that a newer version of MacPorts is available, it
62attempts to update your copy to this version. In that case, the output will be
63different:
64
65[subs="verbatim,attributes"]
66----
67$ sudo port selfupdate
68---> Updating MacPorts base sources using rsync
69MacPorts base version 2.3.0 installed,
70MacPorts base version {manversion} downloaded.
71---> Updating the ports tree
72---> MacPorts base is outdated, installing new version {manversion}
73Installing new MacPorts release in /opt/local as root:admin; permissions 755
74----
75
76TROUBLESHOOTING
77---------------
78If *selfupdate* fails, it usually does so in one of two places: The network
79connection, or the installation of the update.
80
81Network Problems::
82MacPorts uses the 'rsync' protocol to update its sources to the latest version.
83This will fail if you are on a network that blocks TCP connections to the rsync
84port 873. Talk to your network administrators and ask them to allow connections
85to port 873 if this happens to you. Alternatively, you can just download a new
86installer .pkg from macports.org and run that to upgrade your installation.
87+
88Network connection problems might also affect you if you are in a country with
89US export restrictions. We suggest using one of our other
90wiki:Mirrors#MacPortsSource[mirrors] outside of the US in these cases.
91
92Compilation Problems::
93When a problem occurs while building and installing the new MacPorts version,
94you will see the message
95+
96----
97Error installing new MacPorts base: command execution failed
98----
99+
100To find out what went wrong, re-run *selfupdate* with the *-d* flag. This will
101allow you to see all output generated by the build system. Look for the first
102occurance of ``error''. If you cannot figure out what's wrong on your own, feel
103free to ask on mailto:macports-users@lists.macosforge.org[the macports-users
104mailing list] and attach the output generated by
105+
106----
107$ sudo port -d selfupdate
108----
109
110
111SEE ALSO
112--------
113man:port[1], man:port-sync[1]
114
115AUTHORS
116-------
117 (C) 2014 The MacPorts Project
118 Clemens Lang <cal@macports.org>
Note: See TracBrowser for help on using the repository browser.