Re: installer doesn't modify root path

-Original Message- From: Brandon Allbery Date: 2 February 2016 at 16:06:18 > On Tue, Feb 2, 2016 at 9:57 AM, Harald Hanche-Olsen > wrote: > > > Well, you did not say in the bug report that you were using sudo, so no > > wonder it got closed. > > ? sudo is the

Re: installer doesn't modify root path

Well, you did not say in the bug report that you were using sudo, so no wonder it got closed. My own systems are too heavily modified at the moment for me to be sure, but I have a file /etc/paths.d/45-macports containing the two lines /opt/local/bin /opt/local/sbin These should be enough to

Re: installer doesn't modify root path

On Tue, Feb 2, 2016 at 10:22 AM, Harald Hanche-Olsen wrote: > Okay, now I am curious. How does the macports installation manipulate the > path? As far as I know, the above method is standard, even though it may > not be what macports does. (If I installed that file there, I

Re: installer doesn't modify root path

-Original Message- From: Harald Hanche-Olsen Date: 2 February 2016 at 15:57:39 > […] You can check by running “sudo printenv PATH”.  […] Uh, sorry, I missed the fact that you did show the result of running that, and that /opt/local/bin is missing from the output.

Re: installer doesn't modify root path

On Tue, Feb 2, 2016 at 7:22 AM, Harald Hanche-Olsen wrote: > -Original Message- > From: Brandon Allbery > Date: 2 February 2016 at 16:06:18 > > > On Tue, Feb 2, 2016 at 9:57 AM, Harald Hanche-Olsen > > wrote: > > > > > Well, you did not say in

Re: installer doesn't modify root path

On Tue, Feb 2, 2016 at 9:57 AM, Harald Hanche-Olsen wrote: > Well, you did not say in the bug report that you were using sudo, so no > wonder it got closed. > ? sudo is the recommended way to do this. > My own systems are too heavily modified at the moment for me to be

Re: installer doesn't modify root path

-Original Message- From: Phil Oertel Date: 2 February 2016 at 16:31:12 > Entirely possible. I didn't make any such modification personally, but it's > a work laptop, so I don't know what they've done to the image prior to > giving it to me. Maybe I'll get them to

Re: installer doesn't modify root path

On Tue, Feb 2, 2016 at 10:33 AM, Harald Hanche-Olsen wrote: > An alternative would have been to modify /etc/paths instead? Or is that > too global, or something? Same problem, IIRC. -- brandon s allbery kf8nh sine nomine associates

Re: installer doesn't modify root path

-Original Message- From: Phil Oertel Date: 2 February 2016 at 17:13:59 > Yes, it has both env_reset and a secure_path. And some comments at the top > indicating that the file is periodically overwritten by Puppet. Ah, then we have a definite diagnosis! Good. Then

Re: installer doesn't modify root path

-Original Message- From: Brandon Allbery Date: 2 February 2016 at 16:28:50 > The problem with paths.d is that it adds path entries *after* the standard > ones, whereas users tend to expect that e.g. /opt/local/bin/python > "overrides" Apple's /usr/bin/python. So

Re: installer doesn't modify root path

On Tue, Feb 2, 2016 at 7:40 AM, Harald Hanche-Olsen wrote: > -Original Message- > From: Phil Oertel > Date: 2 February 2016 at 16:31:12 > > > Entirely possible. I didn't make any such modification personally, but > it's > > a work laptop, so I

Re:

On Tue, Feb 2, 2016 at 12:35 AM, Ryan Schmidt wrote: > I see a CoreSimulator crash in that log. See > https://trac.macports.org/wiki/ProblemHotlist#xcode7.2 > You are right. Thank you Ryan. Already fixed. -- Eneko Gotzon Ares enekogot...@gmail.com

Re: installer doesn't modify root path

> Am 02.02.2016 um 06:33 schrieb Phil Oertel : > > I'm unable to sudo run any port commands after installing macports (version > 2.3.4, system is El Capitan 10.11.3). I installed via the package installer. > After running the installer and opening a new shell, my login