Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
09-01-2004, 09:32 PM
|
#1
|
|
Member
Registered: Jan 2004
Location: EST
Distribution: Slackware 10.0
Posts: 150
Rep:
|
Pkgtool
I have read the man for pkgtool, but Im still confused. When you installpkg a .tgz, does it need to be a special .tgz that is especially made for pkgtool? Or can I get any .tgz and use pkgtool to install it? Is there anything else I should know, or any tips for using pkgtool? Also, will it work with .tar.gz files? Those are the same as tgz, right?
Last edited by Corallis; 09-01-2004 at 09:36 PM.
|
|
|
|
09-01-2004, 09:38 PM
|
#2
|
|
Member
Registered: Jul 2003
Location: MD USA
Distribution: Slackware
Posts: 136
Rep:
|
Not all .tgz files are Slackware packages. I'm not an expert but I've made a couple of Slackware packages with makepkg, and they are binary files with a directory structure that are copied to your system. Roughly. Someone please correct me if I"m wrong.
|
|
|
|
09-01-2004, 09:48 PM
|
#3
|
|
Senior Member
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914
Rep:
|
Nope.... Your right.
About 90% of all .tgz are precompiled binaries made for slackware. Sometimes you'll find one that is source code... That's pretty rare tho. So basically, you can install any tgz that you find with pkgtool. Whether or not they were made right or even work is another question all together. Thats something you'll have to find out I suppose.
And, no, .tar.gz's are nothing like .tgz's..... .tar.gz's are usually compressed source code that you have to 'configure, make and make install' after you uncompress them... Same thing with .tar.bz2's....
.tgz's are pre-compiled binaries just like .exe or .rpm or .deb.....
Last edited by jong357; 09-01-2004 at 09:52 PM.
|
|
|
|
09-01-2004, 09:51 PM
|
#4
|
|
Member
Registered: Aug 2004
Location: San Diego
Distribution: Slackware
Posts: 303
Rep:
|
You're right, slackware packages are just tarballs with the directory structure of how it'll be installed in the system. The most important thing I guess is the directory structure. I think i've made some tgz's by using tar zcvf .
|
|
|
|
09-01-2004, 10:01 PM
|
#5
|
|
Member
Registered: Jan 2004
Location: EST
Distribution: Slackware 10.0
Posts: 150
Original Poster
Rep:
|
Another question... how do you all generally install files? What I have been doing is this... it may be way off from the "norm", but I never really learned a set way:
(Assuming its a ./configure, make, make install file)
Download said file
tar -xzvf it, assuming its a *.tar.gz
./configure
make
make install
Move all of the old source files to /usr/src
Move all of the new program files to /usr/bin
Is this the standard convention? Or am I way off?
|
|
|
|
09-01-2004, 10:40 PM
|
#6
|
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
It's standart except for moving the new program files, when you issue "make install" you're installing them (they're usually installed to /usr/local/bin instead of /usr/bin) so you shouldn't move them to /usr/bin.
Also try checkinstall it makes a package from the sources you compile so it's easier to install and remove it.
|
|
|
|
09-01-2004, 11:49 PM
|
#7
|
|
Member
Registered: Jul 2004
Distribution: Slackware Current
Posts: 307
Rep:
|
Yup go with checkinstall. Since it will turn it to a .tgz before installing, hence it will be easier to uninstall in the future when you want to get rid of it or upgrade it.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Similar Threads
|
| Thread |
Thread Starter |
Forum |
Replies |
Last Post |
|
pkgtool fails
|
ionmich |
Slackware |
3 |
11-10-2004 07:08 PM |
|
pkgtool does nothing?!
|
alienDog |
Slackware |
8 |
10-31-2004 05:11 PM |
|
pkgtool
|
sio |
Linux - General |
0 |
07-30-2003 12:47 PM |
|
using pkgtool
|
ivans |
Slackware |
2 |
05-28-2003 09:37 PM |
|
pkgtool
|
ktindle |
Slackware |
4 |
12-15-2002 04:14 AM |
All times are GMT -5. The time now is 10:51 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|