[MacPorts] #72510: portconfigure::check_implicit_function_declarations can fail because of permissions error in irrelevant directories

MacPorts noreply at macports.org
Wed May 21 12:52:37 UTC 2025


#72510: portconfigure::check_implicit_function_declarations can fail because of
permissions error in irrelevant directories
---------------------+--------------------
  Reporter:  RJVB    |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  base    |    Version:
Resolution:          |   Keywords:
      Port:          |
---------------------+--------------------

Comment (by RJVB):

 Replying to [comment:1 ryandesign]:
 > Really, you're expected to make the choice for your entire MacPorts
 installation before you install MacPorts.

 That's really not the point here. We all know the dangers of things like
 untested destroot runs with elevated privileges and as a matter of
 principle it should never be allowed to become a habit just to prepend
 `sudo` to every command.

 Esp. not in a development context.

 "Base" acknowledges this through `macportsuser` and by dropping privileges
 for the stages that don't require them, and really the actual configure
 step itself should be included in that as it may have unexpected side-
 effects (the actions that may require root privileges are or can all be
 handled before the actual configure command is run). That's a different
 issue, but addressing it would make the issue at hand independent of
 whether or not `sudo` is used.

 But really, why would errors in `fs-traverse` NOT be ignored in the two
 functions at hand (and why would they check anything other than
 `worksrcpath`, `configure.dir` and `build.dir` as far as those locations
 are distinct)?

-- 
Ticket URL: <https://trac.macports.org/ticket/72510#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list