Description of problem:  get_dso_deps() does not control the environment variable LD_LIBRARY_PATH when tracking down the DSO dependencies of an executable for the install.img.  Because of this, the dependencies may be wrong.  The runtime environment of install.img has a default LD_LIBRARY_PATH [namely, unset].  In practice the bad result might be only a larger-than-necessary install.img: the false dependency may copy some additional libraries, but the actual install-time dependency may be covered by naming the needed libraries explicitly in KEEPFILES.  The bad effects are less unlikely because of the 'chroot' done during the discovery process.  However, it is possible that some executable that requires an unusual library may fail to run during install, because a unique DSO found by LD_LIBRARY_PATH at compose time will be put into a directory that is not searched during install.


Version-Release number of selected component (if applicable):
anaconda-13.26-1.fc13.x86_64


How reproducible: every time


Steps to Reproduce:
1. inspect source code
2.
3.
  
Actual results: File buildinstall.fuctions, function get_dso_deps():
        $(/usr/sbin/chroot $root env LD_TRACE_PRELINKING=1 LD_WARN= \
                                     LD_TRACE_LOADED_OBJECTS=1 $LDSO $bin)


Expected results:
        $(/usr/sbin/chroot $root env --unset=LD_LIBRARY_PATH \
                                     LD_TRACE_PRELINKING=1 LD_WARN= \
                                     LD_TRACE_LOADED_OBJECTS=1 $LDSO $bin)


Additional info: