I just noticed that env-update does not append LD_LIBRARY_PATH variables defined in different files in /etc/env.d, but apparently replaces them instead - only the one defined in the last file shows up in /etc/profile.env.
Is this by purpose, or is this a bug?
Steps to Reproduce:
1. cd /etc/env.d
2. echo "LD_LIBRARY_PATH=/foo1" > 98foo1
3. echo "LD_LIBRARY_PATH=/foo2" > 99foo2
5. grep LD_LIBRARY_PATH /etc/profile.env
I am trying this on a freshly installed AMD64 system. I used the 2005.0 AMD64
CD's and stage3 to install, the last emerge --sync; emerge -u world was done
today. Installed portage version is:
Found it, portage.env_update only puts : in paths that are in special keys.
colon_separated = [
# process PATH, CLASSPATH, LDPATH
for myspec in specials.keys():
if myspec in colon_separated:
specials[myspec].append(varexpand(mycon$ del myconfig[myspec]
# process all other variables
for myenv in myconfig.keys():
since LD_LIBRARY_PATH isn't in color_seperated, no colons get put in and env only picks up the latest entry, not sure if this is a bug or a feature though...portage dudes? :)
Er, there are times when nano sucks, and now is one of them ;) sorry about the $ :0
i'd say use LDPATH not LD_LIBRARY_PATH ... LD_LIBRARY_PATH shouldnt really be abused in this manor ...
This is a WONTFIX then? Or are there ebuilds in the tree that use LD_LIBRARY_PATH?
i dont know of any ebuilds that do and if they exist, they're broken imo
i say this is a WONTFIX ...