port diagnose bug

Brandon Allbery allbery.b at gmail.com
Wed Feb 1 21:06:27 UTC 2017


On Wed, Feb 1, 2017 at 1:42 AM, Ryan Schmidt <ryandesign at macports.org>
wrote:

> It looks like the port diagnose code assumes the path is colon-separated,
> but your fish shell uses spaces to delimit the different paths. I guess
> MacPorts would have to check what shell you're using, and then know how to
> parse each type of shell's idea of how the list of paths is represented.


The $PATH that goes into the environment must be colon separated, or a LOT
of stuff will mishandle it. Including the likes of execlp()/execvp().
(Shells should handle this; after all, csh's $path is space separated / a
csh list, but $PATH in the environment is correctly colon separated.)

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170201/8bd298e2/attachment.html>


More information about the macports-users mailing list