lwasserm and I both suggested "use your distro's package manager", then dxqcanada and dasy2k1 suggested it again. I think it least some of what we were trying to say went over your head. Apologies for not being clear, but it's definitely an important concept.
Here's the scoop:
1. "In the Beginning", installing software was relatively simple. You just copied a program from someplace and ran it. Life was good.
2. There are problems with this "simple" approach:
a) as you accumulate more programs, it becomes harder to keep track of them.
b) Many programs are "inter-related", and/or "share" functionality. One program needs to know about the install status of other programs.
c) Program updates need to know about the install status of the program they're trying to update.
d) etc etc
3. The Windows solution is "add/remove" programs, which typically stores "meta data" about each install in the Windows registry.
It's worth noting that Windows "add/remove" has long been out of control ("Dll Hell"), and newer .Net programs are moving BACK to a "Copy Install" paradigm. But we digress...
4. Linux, on the other hand, still supports "copy install" (when you need it/or want it). It also supports "package managers" (like RPM or DPkg) that manage the same kind of "installation metadata" as the Windows registry.
Linux also supports "copy-build-install" - where you can literally build (and customize) the application in the process of installing it. This is a Good Thing.
5. Most users just want to download a program and start using it. They don't want to mess with "builds", if they don't have to. Linux supports this, too. With graphical front ends (like Synaptic on Ubuntu, or Yast on SuSE Linux.).
6. And thats where we came into the story. We were trying to tell you to use the graphical front end (if at all possible) ... but the specific details will vary from user package to user package, and distro to distro.
Please read this link: good info. It should be of help to you now, and in the future:
IMHO .. PSM