Description of problem: If you install alliance, profile.d/alc_env.csh gets created and in it it modifies your path using: setenv PATH "${PATH}:${ALLIANCE_TOP}/bin:" This ends up putting in a :: into your path. This is a minor security issue as it is easy to run a program unexpectedly when the current working directory is being searched. profile.d/alc_env.sh also has a similar problem. Version-Release number of selected component (if applicable): alliance-5.0-16.20070718snap.fc9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install alliance 2. login again 3. echo $PATH Actual results: Path with :: in it Expected results: Path without :: in it Additional info:
Created attachment 316432 [details] Modified alc_env.csh This is a modified rawhide version of alc_env.csh that doesn't add the current working directory to the path. I also tweaked the manpath to include the defaults in the case that manpath wasn't already set.
Created attachment 316433 [details] Modified alc_env.sh This is a similarly changed alc_env.sh.
alliance-5.0-21.20070718snap.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/alliance-5.0-21.20070718snap.fc9
alliance-5.0-21.20070718snap.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/alliance-5.0-21.20070718snap.fc8
alliance-5.0-21.20070718snap.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
alliance-5.0-21.20070718snap.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.