OK there is no Deb package for this yet and you are going to need to build from
source. That is taking a tar ball package, DL, Unpack, configure, make, and make
install. It a little work, but it can be easy. Warning!! It may give you a
dependency warning, say it may need this library package to order to install.
Thus you going to need to install that to order to install the program. So go
to
sourceforge.net/.../showfiles.php?group_id=2174
Select Linux and DL the tar package. Make sure you save it to your desktop for
easy access. Now we are going to do some mojo. You'll need to open up your
Terminal. That is at Applications>Accessories>Terminal
(The bottom has been taken from http://psychocats.net/ubuntu/installingsoftware)
All so Monkey web sit has even better way too.
monkeyblog.org/.../#installing_a_package_manually
That web site is how I do it. Still you need to install build-essential and how
to do that is found below.
4. Installing from source
Some people prefer to install from source, but I listed it last because it's
what usually scares people off from Linux and makes them think "Why is it so
difficult to install software in Linux?" However, it's still an option, and
unfortunately it's sometimes the only option, depending on how obscure the
software is you're trying to install.
The first thing you'll have to do in Ubuntu is install a meta-package called
build-essential (a meta-package isn't a real package—it's a pointer that tells
Synaptic/Adept/aptitude to install a bunch of other real packages):
sudo aptitude update
sudo aptitude install build-essential
I can't think of a program off the top of my head that I ever needed to install
from source, so I'm just going to make something up—let's call it obscure-1.0.
Most likely, it'll come as zipped file called obscure-1.0.tar.gz. Download this
to your desktop. Then type this in a terminal:
tar -xvzf obscure-1.0.tar.gz
cd obscure-1.0
./configure
make
sudo make install
Installing from source, like the previous two methods, also does not resolve
dependencies—you'll have to install those separately. The ./configure command
may indeed tell you what dependencies you need but in a rather peculiar way; for
example, it will often return with, say, a rather cryptic gtk not found, in
spite of the fact that the user has gtk installed! In fact, what is actually
missing is the gtk development files, libgtkx.y-dev. In general, when it says
can't find library blah and libary blah is already installed, it usually means
that it can't find the blah development files, which can almost invariably be
found and installed by searching synaptic for blah dev. [Most of this paragraph
was contributed by GeneralZod from the Ubuntu Forums—thanks, GeneralZod!]
There's also Checkinstall: Once checkinstall is installed, instead of typing
sudo make install
you type sudo checkinstall -D
and the program creates a .deb file which is then installed. This makes
removing any program compiled from source extremely easy. For more details see
the Wiki: https://wiki.ubuntu.com/CheckInstall. [Most of this paragraph was
contributed by gingermark from the Ubuntu Forums—thanks, gingermark!] Note: in
both Ubuntu and Kubuntu, you can "un-tar" (or unzip) a .tar.gz graphically. I've
never had to use the tar terminal command. To un-tar a .tar.gz graphically, just
open it (double-click usually does this), then click on Extract.