[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 pnewell@…):

 Replying to [comment:4 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.

 Larryv:

 Thanks for the extra information. Yes, this is a non-root install. I must
 admit I kinda wish there had been a way (or at least the documentation
 telling me there was) to install as root for all users (ala Fedora/yum).
 I've been living with (and burned by) "at my own peril" long enough that I
 just take it as part of the price of usage.

 I'm going to have to read up on that "write files to a local directory" as
 I need to better understand what you are saying.

 That being said, I haven't had any problems with MacPorts except for my
 own "duh!" moments and I never argue when things are working (and well I
 might add)

 Paul

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