[MacPorts] #70680: sudo @1.9.16 -- sudo: port: command not found

[MacPorts]

#70680: sudo @1.9.16 -- sudo: port: command not found
---------------------+--------------------
  Reporter:  RobK88  |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.10.1
Resolution:          |   Keywords:
      Port:  port    |
---------------------+--------------------

Comment (by RobK88):

 Setting secure_path will definitely make `sudo` and one's Mac more secure.
 But you will likely get more bug reports when users can no longer use
 `sudo` to execute commands in `/usr/local/bin` etc.

 If you decide to set `secure_path`, I would also recommend updating the
 `notes` section of the portfile to notify users that they will need to
 update the `/opt/local/etc/sudoers` file if they want `sudo` to execute
 commands in paths like `/usr/local/bin` etc

 Personally, I would just comment out the `DEFAULTS secure_path` line in
 the `sudoers` file.  And just tell users to modify the `sudoers` file to
 their needs like before.

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