On Sun, Mar 4, 2012 at 18:43, Sam Kuper <[email protected]> wrote:
> > MacPorts itself does a one-time modification to your profile to edit the > PATH, so that you can more easily run MacPorts and the software it installs. > > I knew about this modification, which is why I was surprised that the > WordNet environment variables weren't also set by MacPorts; but I > hadn't realised that this was the only modification of this kind that > MacPorts makes. > Keep in mind that 1) MacPorts would be very difficult to use without that modification, so there's not really much of a way around it; 2) The choice of whether to modify ~/.MacOSX/environment.plist vs. ~/.profile vs. some other mechanism is controlled to some extent by what will be using the WordNet libraries, so it can't really be made for you. (The environment.plist file controls the environment seen by Aqua GUI applications; ~/.profile is seen only in terminals.) Linux actually has a similar divide if you use something like gdm, but solves it at a different level: the system-wide /etc/profile.d directory for per-package environment modifications. Different desktop environments also have different means of injecting environment variables at the same level as OS X's environment.plist, but last time I looked it was different for Gnome and KDE and I don't know if e.g. LXDE has one at all. -- brandon s allbery [email protected] wandering unix systems administrator (available) (412) 475-9364 vm/sms
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
