On Sun, 27 Feb 2000, George Zeigler wrote:
Besides, aren't there files in the /usr/local/tarball_1 directory which the executable will need to use?
Okay, George, we're getting there ;). The process is like this... I (as a user) download whizbang-0.98a.tar.bz2 into my home directory. In my home directory (or anywhere else, for that matter), I quickly `tar xIvf whizbang-0.98a.tar.bz2', which creates /home/luser/whizbang-0.89a/. I can then cd into ~/whizbang-0.98a/ and configure and build the source into something usable. When I su and `make install', all of the binaries go to /usr/local/bin, and libraries go to /usr/local/lib, and shared files go to /usr/local/share. After that, I can `rm -rf ~/whizbang-0.98a/' without any fear of doing any damage. This entire thread has been based on the assumption on my part that you have been installing the *final* binaries in /usr/local/whizbang-98a/, which you clearly are not. ;) Sorry for the confusion. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x107 | http://www.atipa.com _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/