Fwd: [MacPorts] #45235: Missing MacPorts specific paths in $PATH

[Lawrence Velázquez]

Forwarding from Trac.

vq

Begin forwarded message:

> From: MacPorts <noreply at macports.org>
> Subject: [MacPorts] #45235: Missing MacPorts specific paths in $PATH
> Date: October 1, 2014 at 4:28:10 PM EDT
> To: erik at avalonia.net, macports-tickets at lists.macosforge.org
> Reply-To: macports-dev at lists.macosforge.org
> 
> #45235: Missing MacPorts specific paths in $PATH
> ---------------------+--------------------------------
> Reporter:  erik@…   |      Owner:  macports-tickets@…
>     Type:  request  |     Status:  new
> Priority:  Normal   |  Milestone:
> Component:  base     |    Version:  2.3.1
> Keywords:  path     |       Port:
> ---------------------+--------------------------------
> I operate several servers running assorted software installed with
> MacPorts.
> 
> On a 'no problem' server, I can do:
> 
> {{{
> echo $PATH
> /opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
> }}}
> 
> All good.
> 
> However, I have a problem with one server:
> {{{
> echo $PATH
> /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/local/lib/mysql55/bin
> }}}
> 
> After some research, I still can't locate the correct place to remedy the
> missing paths problem.
> I know I can add the paths with the EXPORT command, but I would like to
> learn the 'correct' place where "/opt/local/bin:/opt/local/sbin:" should
> be located.
> 
> -- 
> Ticket URL: <https://trac.macports.org/ticket/45235>
> MacPorts <http://www.macports.org/>
> Ports system for OS X