Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am new to linux but I've come to the conclusion that you cannot use installpkg to install any tgz (or tar.gz) package. Normally you would untar/unzip the package and then run make and then make install. Does installpkg do that, or does it just unpack the archive? How do I determine whether or not I can use installpkg to install a package, or whether I have to do it manually? I have noticed that whenever I have an rpm file and I run rpm2tgz on it, then installpkg will work fine.
I don't use installpkg, but the pkgtool for .tgz files. do;
$ su - (with the dash), then password.
cd to the dir where tgz files are.
Then use current directory from menu. It will do the complete install.
Probably have better feedback in the slackware group.
the installpkg is slackware thing, there is already compiled program (so no need to run make && make install) in it, so installpkg just unzip the files to /. but it has to be a slackware package. it's similar to RPMs.
The other thing is that when you have some program source codes, you have to unzip/untar it, and than in most cases run configure, make, make install. This will compile the program on your computer.
Ok I see, my mistake was that I thought tar.gz and tgz files were the same thing just with different extentions so you could simply do "mv file.tar.gz file.tgz" and then run installpkg on it.
So let's see if I understand this now, installpkg will work ONLY on packages meant specifically for slackware? The only way to install tar.gz packages is to unpack them then run configure, make and make install (as root).
By the way when I unpack it and then run make and make install, it creates a new directory right in the root directory. Is that supposed to happen? Where are new programs supposed to install to?
you can always run ./configure --help to see what is offered to you. Most of the tarballs are installed under /usr/local unless specified otherwise usually with ./configure --prefix=/path/where/to/intall
The directory which is created when you decompress teh archive is just a handy way to keep all the files needed by the installation process in one place, so you don't cluter your filesystem.
Thanks for the help everyone I just have one more question: How do you uninstall a tarball? I'm assuming you can't just delete the directory, because during installation it copies files to several different directories?
No you can't just delete the directory, if you do that the program still stays on your computer. You have to remove every file that was produced after make install.
If you want to uninstall the slackware package, there is program called pkgtool that might help you
make clean will remove all stuff that configure and make does.
eg, if u type make (you should run it also if you aren't root) the program will be compiled somewhere in the directory where you have unziper the tarball.
Now you can run it from there. When you type make install (you have to be a root to do that) it will copy all program files to your system, so other users can access it.
If you're ever compiling from source, you want a copy of checkinstall handy. Checkinstall replaces the make install step and instead creates a Slackware package from the compiled program and then installs it as a real Slackware package. That means that you can use pkgtool to remove it rather than hoping that the author included a make uninstall.
So bascially, you:
And you have the advantages of compiling it yourself plus the ease of using a Slackware package.
By the way, I think it creates Debian packages and RPMs as well.