[MacPorts] #29708: macports does not properly change PATH environment on installation
#29708: macports does not properly change PATH environment on installation -------------------------------------+-------------------------------------- Reporter: sorin.sbarnea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: -------------------------------------+-------------------------------------- It look that the *only* way to update PATH enviroment on OS X for all users and all kinds of applications (console or GUI) is to modify /et/launchd.conf Currently macports does not do this. Refference http://stackoverflow.com/questions/135688/setting-environment-variables- in-os-x -- Ticket URL: <https://trac.macports.org/ticket/29708> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29708: macports does not properly change PATH environment on installation -------------------------------------+-------------------------------------- Reporter: sorin.sbarnea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: | Port: -------------------------------------+-------------------------------------- Changes (by ryandesign@…): * component: ports => base Comment: The request to update the PATH of all users, instead of just the user who is logged in at the time that MacPorts is installed, is a duplicate of #24930. The request to update PATH for GUI apps in addition to console apps is new AFAIK. What apps would benefit from this change? I'm not familiar with /etc/launchd.conf or the implications of using it instead of or in addition to what we already do. -- Ticket URL: <https://trac.macports.org/ticket/29708#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29708: macports does not properly change PATH environment on installation -------------------------------------+-------------------------------------- Reporter: sorin.sbarnea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: | Port: -------------------------------------+-------------------------------------- Comment(by sorin.sbarnea@…): Yesterday I found the first application that was failing to detect `hg` because the tool was not found in path (PyCharm). I studied the issue because previously I have similar issues on OS X, and I discovered that the only way to modify the path for the entire system and all applications is `/etc/launchd.conf` which by the way is empty by default. The idea is thay GUI application that will want to use a macport installed command will fail if we do not update the PATH for gui applications. -- Ticket URL: <https://trac.macports.org/ticket/29708#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29708: set PATH globally in /etc/launchd.conf --------------------------------------+------------------------------------- Reporter: sorin.sbarnea@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: Resolution: wontfix | Keywords: Port: | --------------------------------------+------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => wontfix * version: 1.9.2 => * type: defect => enhancement Comment: Changing the environment for all apps is a really bad idea. Anything that assumes that the commands it runs are the Apple-supplied versions will break when the MacPorts ones behave differently. GUI apps shouldn't rely on PATH having a particular value anyway. -- Ticket URL: <https://trac.macports.org/ticket/29708#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts