The general advice on tarballs for ubuntu users seems to be avoid them at all costs.

That's OK as there's so much available in the repositories, but sometimes I really want to use a tarball that's maybe come from a Linux mag.

Now, they've gotta be 100% safe. Right?

I've wiki'd the ubuntu formums and I haven't found anything that works for me. It might be because I'm still a newbie, but I feel really stupid that I can't install from source.

I can get through to the unpacked stage, but when I go for "./configure" it all goes wrong. The official ubuntu documentation is not really helpful - I don't think ubuntu encourages tarball usage - and I've found nothing else useful on Google, or on the contributed ubuntu documentation that explains the process in the detail required.

Can anyone point me in the direction of a really simple idiot-style guide to getting tarballs working and installed. Generally, but especially in ubuntu.

As I said, I've tried to install .tars from Linux mag DVDs without success. And there can't be any security issues there.

I've gradually converted many of my friends and family to ubuntu, but I'd love to show them some decent games that are only available in tarball format.

One example is sturmbahnfuhrer which looks great from the screen shots (a bit like micro-racers).

Any help will be appreciated - and the simpler the better. I really need the hand-in-hand approach to get through this, starting from the very beginning.

First--if possible--always use the package manager to install SW. It is by far the most painless method.

Second, you do not "install tarballs". A tar archive (which may or not be compressed) can contain just about anything--files, scripts, binary code, source code, pictures of your kids. The files necessary for installing SW often come packaged in a tar or tar.gz--or similar-- format.

If the "tarball" contains files to install SW, at least three forms might be found:
1. package files--eg .rpm or .deb
2. executables + maybe an install script
3. source code which must be compiled.

Often, you simply have to unpack the archive to see what is there. Ideally, in the unpacked directory, you would find instructions.

The best way to deal with "tarballs" is on a case by case basis. After awhile, you will know what to look for.

Again--always try the package manager first.

If you need to install a program from source that comes in a tarball, make sure that you install the build-essential package using aptitude first. This will allow most source distributed programs to compile OK.

If ./configure gives you errors, read the documentation and ask questions about what they mean. Then fix the problem and try again.

As Pixellany suggested, always use the package manager if you can. There are about 20000 packages in the Ubuntu repos, if you enable the universe and multiverse repos.

--Ian

Something else to remember is that if your distro uses rpms or debs, try to always stick to them. The problem is that if a program depends on the tarball you have installed the system database will not be aware of it. This will then cause you to write a post saying "I installed X but the system can't find it"

And if you still want to install from source, please post the error message you get so that we can try and explain.

Sound advice, guys. Thanks. I guess it does make sense to stick to debs as much as possible. I'll definitely enable universe and multiverse now.

I see by the way what you mean pixellany about not "installing" tarballs. I've checked some out and now understand that a tarball is just a package with loads of elements inside.

However, if I do try another source-build, I will post the error message.

Cheers.

eoinrua; do you have Ubuntu's linux headers installed? try this:

[HTML]sudo apt-get install linux-headers-$(uname -r)[/HTML]

then try to run /.configure, make, make install again. you may just need a configured kernel source tree?

Not all deb packages are equal and some deb packages won't work with Ubuntu because they are intended for a different Debian based distribution. When I use a deb package that's not in the Ubuntu repository I make sure its intended for Feisty which I run. ./configure executes a shell script provided by the package author. The quality and completeness of these scripts can impact the difficulty of compiling and integrating a package. Name the script configure is standard but not required. If there's no configure file check the readmes included to discover the script name. As a rule, difficulty with compiles relates to not having both the required libraries and their "-dev" packages installed. Sometimes a particular version of a library is required and you may be running a different one. Changing library versions to accommodate one package has the associated risk that other applications you're running won't run with the replacement. This is one of the values of a distribution like Ubuntu. All the packages in the repositories are compatible with each other from a dependency perspective. The issues surrounding the compiling of tar balls are more a Linux thing and not necessarily the fault of Ubuntu.

Hi,

No, I don't have the headers installed or, initially, the build-essentials. I now have the build-essential package and I'll apt-get the linux-headers before trying again.

As I said in my first post on the thread, the repository packages are great and so easily installed. Just now and again, though, I come across something that's not available in the usual way. That's the only reason I'm going to the bother of source-based install.

I'll let you know how I get on.

When otherwise not available I will and have compiled drivers. Webcam is one example. I also install the flash binaries as provided on the Adobe site. Each release of Ubuntu does a more complete job of meeting my needs and the number of necessary compiles diminishes with each new release.

Using the package manager for all software maintenance is not always the best solution.
I do not reject the use of the package manager, but sometimes it is better to compile and install apps independently.
For instance, with Ubuntu 7.04 come Firefox, Thunderbird, Pan, to mention a few apps.

If you rely on the package manager your version of these apps will be outdated.
Firefox has a complete new release that solves many security problems.

The versions of Firefox and Thunderbird that came shipped with Feisty Fawn do not allow automatic updates from the Firefox and Thunderbird sites, and you have to depend on the software development team that prepares patches and updates for your release.
So you have to live with a browser that is not really safe to use.

The version of Pan that came with Feisty Fawn (0.120) contained bugs that, in many occasions, made downloading impossible. So I downloaded the latest version, compiled and installed it, and the bugs were gone.

Another good reason for the use of the "./configure, make, make install" method is the educational side of it.
Many Linux newbies lack basic knowledge, like handling tarballz or compiling a source, merely because they are still "windowsed".
Using Linux also means being independent, isn't it?

A long-finished thread but, just in case it passes into a vacuum, I have to say sjonnie that as a student of Latin I really admire your signature...

Sjonnie had some excellent points. Based the stated criteria I'd be inclined to agree. You do however loose the ability to to do an upgrade. For new Linux users who can't really fix the problems that can come up, the Ubuntu repositories and package manager are a better choice.