Picture of installing tar.gz or tar.bz2
Let's say you are a moderately experienced Linux user, and you want to install an application off the Internet but it doesn't have a nice package that works on your system.
A lot of users, even quite experienced ones, have issues with going from the tarball to the installed program because they just do not know the fairly easy steps required to get the job done. But it's only easy if you already know how to do it! So, here's a quick instructable about how to install stuff from developer sites.

Tarball def: Tarballs are a large collection of files assembled into a single archive file. The "tar" command is used to combine many files into a single file for archiving or easy distribution. The "gzip" command is used to compress the size of a file so that it takes up less space. A tarball is very similar to a .zip file on Windows, or a .hqx, .sit, or .dmg file on Macs.
Tarballs have extensions like ".tar.gz", ".tar.bz2" or "TGZ". Most of the time, a tarball contains source files and/or binary files. In the open source community, they are used to distribute source code. If you find any software with a .tar.gz appendix, you will need to uncompress it by double clicking on it before installing the software it contains. To do the same thing from a terminal window, you can also use the tar command like this:
tar -xzf name_of_file
Source files are nothing but raw code which requires compilation to work, while binary files are like .exe files which are ready to install.
Remove these adsRemove these ads by Signing Up
cld00001 year ago

How would I go about compiling a source tarball that doesn't have a configure or a Makefile (because there are some packages that newer than what my distribution's repos have that don't have a configure script or a Makefile).