Opened 12 years ago

Last modified 12 years ago

#36950 assigned defect

Local Port Repo Instructions Should Address Permissions Issue

Reported by: dave@… Owned by: larryv (Lawrence Velázquez)
Priority: Normal Milestone:
Component: guide Version:
Keywords: Cc: cooljeanius (Eric Gallager)
Port:

Description

The many tickets complaining of permissions issues on local portfile repos are evidence that the instructions at http://guide.macports.org/chunked/development.local-repositories.html should be updated. In particular, it may well be that the requirement that portfiles be readable by "nobody" make it inappropriate for most users to store the ports under their home directories, as the ticket suggests. Also, the ticket should suggest specific permissions and ownership for local portfile repos that will help avoid this issue, and suggest sudo -u nobody ls <directory> as a test

Change History (6)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Component: portsguide
Owner: changed from macports-tickets@… to markd@…

Yes, ever since we merged the GSoC '08 privilege-dropping branch into trunk, those instructions have been out of date. I don't know how the instructions need to be changed to make them valid again. If anybody else does, patches to the guide XML files would be welcome.

BTW it's not the "nobody" user that needs to be able to read the portfiles; it's the "macports" user.

comment:2 Changed 12 years ago by dave@…

For me, locating the repository under /Library/ was enough to make it work.

comment:3 Changed 12 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:4 Changed 12 years ago by cooljeanius (Eric Gallager)

I think #38216 is a duplicate of this

comment:5 Changed 12 years ago by larryv (Lawrence Velázquez)

Owner: changed from markd@… to larryv@…
Status: newassigned
Version: 2.1.2

I opened #38216 for my todo list. I guess I’ll just take this one instead.

comment:6 in reply to:  1 Changed 12 years ago by jmroot (Joshua Root)

Replying to ryandesign@…:

BTW it's not the "nobody" user that needs to be able to read the portfiles; it's the "macports" user.

It's whatever macportsuser is set to in macports.conf.

Note: See TracTickets for help on using tickets.