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.
check out a prog called checkinstall. When u are installing from a source, checkinstall makes a package with all the file that were compiled. So that you can distribute the file in a simple package format later, or when u want to uninstall the prog for whatever reason, u can just use simple removepkg or rpm -e or whatever. As far as i know, checkinstall makes 3 different types of packages, one for tgz, rpm, and deb..
go to freshmeat.net and check it out
Originally posted by digiot The only tool you need is a command line.
tar -xzvf filename
./configure
make
su
make install
If you have any problems, you'll need to check the scripts and see if you can edit anything - such as your libraries being in a weird place when the script expects them somewhere else, but that's rare and you should be okay in Slack.
Of course, you may not have the libraries and whatnot needed, but then just download them and start the process over again. Good luck.
- Sorry. Dain bramage. Somebody in a thread I was just reading was using Slack. Duh.
What if its on cd do you have to just write the file name or the whole description on where it is?
Quote:
Originally posted by digiot The only tool you need is a command line.
tar -xzvf filename
./configure
make
su
make install
whats with confirgure,make,su,make install?? why cant you just write tar -xzvf "filename"?
or you have to write all the combinations in one sentence like this tar -xzvf "filename ./configure make su make install?
What if its on cd do you have to just write the file name or the whole description on where it is?
You would have to tell it where it is
tar -zxf /mnt/cdrom/file (if that is where you mount your cd's)
Quote:
whats with confirgure,make,su,make install?? why cant you just write tar -xzvf "filename"?
or you have to write all the combinations in one sentence like this tar -xzvf "filename ./configure make su make install?
No, those are all separate commands. First you extact it, then you configure it, then you make (compile) it, then you install it.
tar (enter).....no news is good news
./configure (enter)....if it went through the configure with no errors then move on.....if you got errors then you have to see what they are about
make (enter) same as above witht the errors
su (enter) this changes you to root so you can write to the directories where the files go
Yeah - sorry - I put them on separate lines meaning they're separate commands. Unless something's on the path (which is usually just bin-type directories) you're always going to have to put full pathnames.
So the command to untar/zip is:
tar -xzvf /mnt/cdrom/filename.tar.gz
If it's just an uncompressed tar, it's
tar -xvf blahblah
and so on for other archive and compression formats. (man tar for all that.)
And then you cd to the directory, such as /where you installed it/filename - you can cat the INSTALL and README and other doc files if you want (good idea, but not always necessary).
And then you configure it:
./configure
Then build it:
make
Then su to root, type in your password and install:
make install
As long as the libraries are found and the directory structure is good and the system is capable and so on, you've got a program. You can run programs - say you're doing joe - in between make and make install you can type ./joe, I think, and it should run. So you know everything's good. So then make install. The scripts will generally send it to /usr/local/bin along with man pages to /usr/local/man and so on. /usr/local/bin should already be on your path, so type in the app name and it runs.
But as far as just untarring - like say it's some of your personal files that aren't executable, yeah - 'tar -xzvf /mnt/cdrom/files' will untar them and you can 'fooeditor foofilename' or whatever you want to read/edit them. The rest of the stuff is just for compiling. Oh, and as far as your libraries, those'll probably go to /usr/local/lib as they aren't executables so much as for executables.
-- Oops. I was typing slow while you were editing - this is kind of a pointless post now. *g*
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.