Re: /etc/paths
On Feb 8, 2015, at 5:10 AM, Richard L. Hamilton rlha...@smart.net wrote: ~/.launchd.conf (or /etc/launchd.conf systemwide) can provide ways to set the PATH for the per-user launchd instances. See launchctl man page for the latter - basically a setenv key valuelaunchctl command. The Yosemite man page for launchd.con says that ~/.launchd.conf was never implemented (and won’t be) while /etc/launchd.conf is no longer used. This seems to be true. I can verify that /etc/launchd.conf is ignored. I never tried to use ~/.launchd.conf. What I do is export some environment variables using launchctl in my shell login script. Not ideal, but at least they are set after I login in Terminal, which generally happens pretty early in any session. Note that the launchctl setenv command (and unsetenv and getenv) is deprecated in Yosemite. When they are removed I don’t know of any other way to set environment variables for the Aqua environment. Mike ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Feb 7, 2015, at 4:01 AM, Luc Bourhis luc_j_bour...@mac.com wrote: (1) We consider /etc/paths to be a system file. We don't like modifying system files. (2) Modifying /etc/paths affects all users' settings, which is undesirable. Actually it is desirable, or it has at least been desired by some users, e.g.: https://trac.macports.org/ticket/36323 Note that it was suggested in this discussion you linked to add files in /etc/paths.d but that would not do what many users want because the paths listed in /etc/paths are put first in PATH and then those from /etc/paths.d are appended. Since /etc/paths lists /bin, /user/bin, etc by default, Macports paths would not override system ones. I like it the other way around and I am not the only one I think. I am happy to see that my initial noise led to informative a discussion after all ;-) And then there the orthogonal issue of Apps launched from the Finder which get PATH from launchd and for which neither path_helper nor shell startup files help. Once upon a time, I hacked a solution with a daemon watching .bashrc and friends to keep the PATH of the shell and that of launchd in synch but eventually I gave up and just launched the PATH-sensitive Apps with open from the Terminal. ~/.launchd.conf (or /etc/launchd.conf systemwide) can provide ways to set the PATH for the per-user launchd instances. See launchctl man page for the latter - basically a setenv key valuelaunchctl command. There also used to be ~/.MacOSX/environment.plist, (see https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html ), but reports suggest that’s no longer used since Lion (or possibly Mountain Lion). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
(1) We consider /etc/paths to be a system file. We don't like modifying system files. (2) Modifying /etc/paths affects all users' settings, which is undesirable. Actually it is desirable, or it has at least been desired by some users, e.g.: https://trac.macports.org/ticket/36323 Note that it was suggested in this discussion you linked to add files in /etc/paths.d but that would not do what many users want because the paths listed in /etc/paths are put first in PATH and then those from /etc/paths.d are appended. Since /etc/paths lists /bin, /user/bin, etc by default, Macports paths would not override system ones. I like it the other way around and I am not the only one I think. I am happy to see that my initial noise led to informative a discussion after all ;-) And then there the orthogonal issue of Apps launched from the Finder which get PATH from launchd and for which neither path_helper nor shell startup files help. Once upon a time, I hacked a solution with a daemon watching .bashrc and friends to keep the PATH of the shell and that of launchd in synch but eventually I gave up and just launched the PATH-sensitive Apps with open from the Terminal. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
And then there the orthogonal issue of Apps launched from the Finder which get PATH from launchd and for which neither path_helper nor shell startup files help. Once upon a time, I hacked a solution with a daemon watching .bashrc and friends to keep the PATH of the shell and that of launchd in synch but eventually I gave up and just launched the PATH-sensitive Apps with open from the Terminal. Ok, how do you adjust launchd's concept of PATH? Anything that I can find to adjust launchD requires running launchctl, which is done after logging in, after apps have started up. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Feb 6, 2015, at 1:49 PM, Michael keybou...@gmail.com wrote: On 2015-02-06, at 10:25 AM, Luc Bourhis luc_j_bour...@mac.com wrote: Not launchd, no. It's for the shell and it helps with MANPATH too. man path_helper for the details. Interesting. I'm surprised MacPorts doesn't stuff something in there. (1) We consider /etc/paths to be a system file. We don't like modifying system files. (2) Modifying /etc/paths affects all users' settings, which is undesirable. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On 2015-02-06, at 10:25 AM, Luc Bourhis luc_j_bour...@mac.com wrote: On 6 Feb 2015, at 19:21, Michael keybou...@gmail.com wrote: Shame on me! You are right. This is a new computer and /etc/paths did not get copied from the old one as I thought. Sorry for the noise and thanks for your patience! /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? Not launchd, no. It's for the shell and it helps with MANPATH too. man path_helper for the details. Interesting. I'm surprised MacPorts doesn't stuff something in there. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Fri, Feb 6, 2015 at 1:49 PM, Michael keybou...@gmail.com wrote: Interesting. I'm surprised MacPorts doesn't stuff something in there. In the past, it forced paths from /etc/paths after the system ones, whereas people tend to want MacPorts installs to override system ones. I don't know if this is still true. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Feb 6, 2015, at 2:09 PM, Lawrence Velázquez wrote: (1) We consider /etc/paths to be a system file. We don't like modifying system files. (2) Modifying /etc/paths affects all users' settings, which is undesirable. Actually it is desirable, or it has at least been desired by some users, e.g.: https://trac.macports.org/ticket/36323 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
/etc/paths
Shame on me! You are right. This is a new computer and /etc/paths did not get copied from the old one as I thought. Sorry for the noise and thanks for your patience! /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On 6 Feb 2015, at 19:21, Michael keybou...@gmail.com wrote: Shame on me! You are right. This is a new computer and /etc/paths did not get copied from the old one as I thought. Sorry for the noise and thanks for your patience! /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? Not launchd, no. It's for the shell and it helps with MANPATH too. man path_helper for the details. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Fri, 6 Feb 2015, Michael wrote: /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? And what other little secrets are there? I've learned more about OSX from reading this list than from anywhere else, and I go back Unix-wise for 40 years! I have the Big Dummies ebook, but I'd like to see a Guru's Guide... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
