[SOLVED] difference of using tar.gz or rpm to install package
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
difference of using tar.gz or rpm to install package
I know package can not install by tar.gz or rpm way , if I install it with tar.gz way by using default setting setting ( do not change any path , parameter etc. ) , is it the same as by using rpm ?
Install by tar.gz, you mean from the sources and compile it ?
Often distributions changes things when they packages software. So no, you can't be sure it is the same thing. A lot of options are available when compiling.
And using rpm (or any official distro's packages) allow you to easily upgrade or remove packages. From source it is a bit harder.
as above , no it is not the same .
However you can make a rpm from the source code using "rpm-build" and install with your package manager ( yum/dnf/zypper)
dependency check (although autoconf, often used to put a tarball together, checks dependencies as well)
you can install binaries
you get a database of all your installed software
thanks to the DB, you can verify, remove or update software with ease
Perhaps a few more.
EDIT disadvantages: tar and compilers are available on all platforms, not rpm. And when you use tar, you are forced to do more manual work and be more thorough, which can be considered a plus.
Last edited by berndbausch; 11-12-2018 at 12:55 AM.
In additions to the answers above, are you presented with either a .tar.gz tarball or a .rpm file download choices? If that is so, most of the time the .tar.gz file contains the source code (which you can compile on different platforms), and the rpm file contains the RPM installer (which of course you can only run on RPM-based systems).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.