Another stupid-a$$ newbie "how do I install xyz" thread
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
Another stupid-a$$ newbie "how do I install xyz" thread
Sorry guys, but I have looked around and I can't find an explanation of how to install stuff that comes in various flavors of gzips and tarballs.
I know that for Slackware packages we can use pkgtool that came with the installation disk. But what about stuff that people package for generic linux that we want to install on our systems?
How do I control where the stuff gets extracted to? It seems like when these packages are extracted they automatically go into different directories, how do I know they're in the right place?
How do I keep track of where all this stuff goes so I can remove it all cleanly if/when I want to?
How do I know which options to use on the various gzips and tarballs like .tar, .tar.gz, .tgz, tar.bz2, etc. (did I miss any?)
.tar.gz - tar zxvf (see the manpage for what each letter does, some aren't necessary)
.tar.bz2 - tar xjvf
.tar - tar xvf
.tgz - you can use zxvf, but these are usually packages
Usually it goes as:
./configure (don't forget to read INSTALL, README, and go throught ./configure --help so you can see what changes you can make)
make
make install
make install, puts them where they're supposed to belong usually somewhere inside /usr or /usr/local.
uninstall is done by 'make uninstall'. But you either need to keep the directory where you extracted it AND where you ran ./configure
OR you can just extract it to some directory later and run the configure script again. (Hope you understand the difference,
You need to be root to do 'make install' or 'make uninstall' for most software since it involves either copying or deleting files from system dirs.
I would recommend doing './confgure' and 'make' as normal user tho or you may have permissions problems accessing some files when running software as user
You can also try checkinstall instead of "make install". This is how I install self compiled software. checkinstall automatically creates a Slackware package and installs it. So you can uninstall it with removepkg or pkgtool.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
Quote:
Originally Posted by pdw_hu
.tar.gz - tar zxvf (see the manpage for what each letter does, some aren't necessary)
.tar.bz2 - tar xjvf
.tar - tar xvf
.tgz - you can use zxvf, but these are usually packages
Usually it goes as:
./configure (don't forget to read INSTALL, README, and go throught ./configure --help so you can see what changes you can make)
make
make install
make install, puts them where they're supposed to belong usually somewhere inside /usr or /usr/local.
uninstall is done by 'make uninstall'. But you either need to keep the directory where you extracted it AND where you ran ./configure
OR you can just extract it to some directory later and run the configure script again. (Hope you understand the difference,
Thanks for the options you mentioned. I guess I don't even know what to ask, but I was talking about executables rather than building from source. For example, I tried to install ROX, but it didn't work. I was able to extract it ok (I think) but I didn't get to choose which directories it went into. And then when I wanted to delete it, I had to find all the pieces and delete them all, I didn't know how to execute one command and delete all the modules.
When you say that "make install puts them where they're supposed to be" are you saying that when you install stuff you don't have any choice? The extraction just builds whatever it wants? Or maybe this was during ./configure where you specified which directories it went into???
I didn't understand your last comments about needing to keep the directory when it was extracted.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
Quote:
Originally Posted by dive
You need to be root to do 'make install' or 'make uninstall' for most software since it involves either copying or deleting files from system dirs.
I would recommend doing './confgure' and 'make' as normal user tho or you may have permissions problems accessing some files when running software as user
I don't understand the difference between make and make install. Are you talking about doing a compilation as a user and then installing the binaries as root?
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
Quote:
Originally Posted by dom83
You can also try checkinstall instead of "make install". This is how I install self compiled software. checkinstall automatically creates a Slackware package and installs it. So you can uninstall it with removepkg or pkgtool.
You will find checkinstall in extra/
This sounds very cool but I don't have an /extra directory, at least not at top level. What is the path to this? And I couldn't find checkinstall with whereis.
I also don't understand what you mean about self compiled software.
Handy references are http://www.slackersbible.org/book/ package mgt section and similar section in Slackware Linux(Slackware Linux essentials) by Alan Hicks and others available at linuxpackages documents section for an on-line version. Those are good start-off points as well the man refs.above. Happy slacking
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
I didn't find what I was looking for in those books, but I'll go back and look again. In the meantime I used what I read in this thread and I was able to compile and install something. It will be interesting to see if I can also get rid of it all!
'make' compiles and 'make install' installs it (basically copies it).
as for installation directories, ./configure --help lists you some command line options (--help is one of them for ex.) which you can override the defaults.
executables can be put whereever you want basically and ran by ./file
as for the uninstall issue:
let's say you extracted something, did ./configure,make and make install. then deleted that directory.
after a while you want to uninstall that program.
you can either search for all the files for that program (but then it's easy to miss something)
or you can just extract the source again, run ./configure then do make uninstall (as root, sorry i didnt mention that before). or you could just backup the first directory, but that takes up lots of place.
This sounds very cool but I don't have an /extra directory, at least not at top level. What is the path to this? And I couldn't find checkinstall with whereis.
I also don't understand what you mean about self compiled software.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
Thanks guys, you are great. I can't claim to understand it completely, but after downloading the source for cronky and compiling and installing it, I am further than I was before.
I have all the CDs...so I'll look for it there on the /extra directory.
Usually executables are put in /usr/bin or /usr/local/bin. If the program is put in /opt then then it's /opt/some/dir/bin (for example: /opt/kde/bin).
If the location is in your PATH (try "echo $PATH"), then you can just type the name of the program. If not, you must give the full path (/opt/kde/bin/kruler, for example). I manually add stuff to the K menu (or in your case it would be the Gnome menu) for programs I want to run (like Neverball).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.