[opensuse] How To Install For File With Extension .tar.bz2 Or .tar.gz ?
Hello, I am newbie of OpenSuSE 10.3 (KDE), could you please advise me on how to install software in which the downloaded file which have extension .tar.bz2 or .tar.gz Thank you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sun, 11 Nov 2007, by williamkow@yahoo.com:
Hello, I am newbie of OpenSuSE 10.3 (KDE), could you please advise me on how to install software in which the downloaded file which have extension .tar.bz2 or .tar.gz
These files are so-called zipped tars or 'tarballs'. A 'tar(1)' (tar == 'Tape-ARchive) is a collection of files, concatenated and with some error-detection header added. Run a tar through a zip program as gzip(1) or bzip2(1) and you get a file commonly denoted as .tgz, .tar.gz or .tar.bz2 Unpacking can be done in either two steps, with 'bunzip2 file.tar.bz2' or 'gunzip file.tar.gz' followed by untarring the tar file with 'tar -xf file.tar' It can also be done in one step with tar's builtin zip as 'tar -xzf file.tar.gz' or 'tar -xjf file.tar.bz2' You'd be wise to look inside the tar file first, to make sure the file have been put in their own directory, otherwise your $HOME might be flooded with dozens of files. So first: 'tar -tzf file.tar.gz' or 'tar -tjf file.tar.bz2' If the files are not in their own directory, make one first and place the tar file there before untarring. Most likely the files inside the tar belong to a program in source-code, which you have to compile before you can run the program. Luckely, most source file programs are made with the help of autoconf(1), which gives the end-user a 'configure' script to adapt the program to his own environment. Run 'configure --help' and you see several options to further adapt the program to your liking. After 'configure' has finished, it leaves a 'Makefile' script, which is used by 'make(1)' to finely compile the program into an executable. The last step is to install the executable, together with man-pages and configuration files. This can be done with 'make install', or with 'checkinstall', which makes an rpm file for you.
Thank you.
HTH Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.20 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 11 Nov 2007, Theo v. Werkhoven wrote:- <snip>
Most likely the files inside the tar belong to a program in source-code, which you have to compile before you can run the program. Luckely, most source file programs are made with the help of autoconf(1), which gives the end-user a 'configure' script to adapt the program to his own environment. Run 'configure --help' and you see several options to further adapt the program to your liking. After 'configure' has finished, it leaves a 'Makefile' script, which is used by 'make(1)' to finely compile the program into an executable.
The last step is to install the executable, together with man-pages and configuration files. This can be done with 'make install', or with 'checkinstall', which makes an rpm file for you.
There's also the possibility that the archive contains a spec file that can be used to build the rpm as well. If one is present, using one of the commands: rpmbuild -ta $archive.tar.bz2 rpmbuild -ta $archive.tar.gz rpmbuild -ta $archive.tgz will have rpmbuild go through the following sequence: 1, make sure that any build dependencies are satisfied; 2, unpack the sources; 3, apply any patches that are required; 4, possibly create a new "configure" script to match the build system; 5, if a "configure" script is present, execute it so the executable will reference libraries on that particular system; 6, call make to build the executable; 7, "install" the application, documents, etc. into a temporary build environment; 8, create a binary rpm from the temporary build environment, ready for installing, and a source rpm from the original source archive. Not all these steps occur every time a package is built, and most often step 4 isn't present. If there are no patches to apply, neither will step 3. So, probably the simplest way would be to try rpmbuild first. If it builds properly, you get a package to install. If dependencies are missing, install those and rebuild. If there is no spec file, a bit more work is required, as described by Theo above. As for the choice between using either "make install" or "checkinstall", using checkinstall will create a package that can be installed and noted in the rpm database, whereas "make install" doesn't. The advantage is that, if at some point you try to install another rpm package that conflicts, you get to know about it before you suffer from unexplained problems. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-11-11 at 17:08 +0800, williamkow wrote:
Hello, I am newbie of OpenSuSE 10.3 (KDE), could you please advise me on how to install software in which the downloaded file which have extension .tar.bz2 or .tar.gz
Read the instructions on the site you got that archive from - any other advice can be easily wrong as we don't know what type of archive you got: tarred sources, tarred binaries, whatever. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHN2N8tTMYHG2NR9URAiY6AJ9ERLFjV6+qyS6BtnXWhupjptuyvACfanL7 v8QZ7863BJ3jRBeJ2TfPjS4= =E3ot -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
David Bolt -
Theo v. Werkhoven -
williamkow