[MacPorts] #41272: problem with selfupdate

[MacPorts]

#41272: problem with selfupdate
------------------------+--------------------------------
  Reporter:  pnewell@…  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.2.1
Resolution:  invalid    |   Keywords:
      Port:             |
------------------------+--------------------------------

Comment (by larryv@…):

 Replying to [comment:2 pnewell@…]:
 > I added the sudo and it worked like a champ. I did notice that the
 > next step "port upgrade outdated" does give me an "insufficient
 > privledges" message if I don't preface the command with sudo.
 >
 > I am now "selfupdated-ed" and I suspect I will remember the 'sudo'
 > thanks to my mistake in thinking it was a possible problem ("duh!"
 > moments have good memory retention)

 The documentation often fails to note when superuser privileges may be
 necessary. Generally speaking, commands that make changes require root:
 - `sudo port selfupdate` / `sudo port sync`
 - `sudo port install foo` / `sudo port uninstall foo`
 - `sudo port activate foo` / `sudo port deactivate foo`
 - `sudo port upgrade foo`
 - `sudo port setrequested foo` / `sudo port unsetrequested foo`
 - `sudo port select --set foo foo-x.y`
 - etc.

 Commands that are purely informational don’t need root:
 - `port info foo` / `port variants foo`
 - `port contents foo`
 - `port deps foo` / `port dependents foo`
 - `port installed`
 - `port echo foo\*` / `port list foo\*`
 - etc.

 Some commands that write files default to using a local directory in the
 absence of superuser privileges (`~/.macports` on my machine):
 - `port fetch foo`
 - `port configure foo`
 - `port build foo`
 - etc.

 And of course, if you have a non-root MacPorts installation, you’re aware
 of what you’re doing and proceed at your own peril.

-- 
Ticket URL: <https://trac.macports.org/ticket/41272#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X