Qt libraries have been using RPATH for a long time, thus obsoleting the need to modify LDPATH to specify their custom locations. If nobody can find a valid reason for /etc/env.d/44qt4 to exist, I propose to stop installing it. ( http://blog.flameeyes.eu/2008/12/30/avoid-ldpath-pollution )
I tried this and all hell broke loose. Didn't rebuild world yet, but there were quite a few packages that stopped working or broke during compilation after removing it. I'll have to do more testing...
We removed RPATH from all qt libraries in 4.8+, so I don't know if this is still feasible...
(In reply to comment #2) > We removed RPATH from all qt libraries in 4.8+, so I don't know if this is > still feasible... Closing. In this case it's actually better to add an LDPATH entry than using RPATH, since Qt doesn't install any private libraries nor any plugins there (the subdir is needed just for slotting) and runpaths make more sense in executables.