mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Dec. 09 2005,16:56 |
 |
I think the most effective way is to learn how the filesystem hierarchy works. Applications are usually installed with a specific arrangement of directories. If you know or discover the prefix of an app's installation, for example /usr/local or /opt/something, most apps will have their executable(s) installed in $PREFIX/bin. Docs, examples, images, etc will be in $PREFIX/share. Often there is a subdirectory with the same or similar name as the name of the application, so finding which files to remove is not usually a huge task. Firefox is an exception, since its files are all within a single directory. Although it's in /usr/local, it uses a directory structure normally reserved for apps in /opt.
The only big problem is deciding whether the files you remove are needed by other programs. You often see this with libraries ($PREFIX/lib), so i tend to leave libs alone unless I'm absolutely sure they are not needed by other programs.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|