SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I just converted to Slack I like the idea of never having to use rmps again and doing everything from source.. but I just noticed that pkgtool needs .tgz files to install from.... but most source downloads that I have come across are as tar.gz . What is .tgz ? Please excuse my ignorance on this one...
so if they are both gzipped tarballs, then does that mean I always have to rename the archive from asfd.tar.gz to asfd.tgz for pkgtool to see it? Maybe I have just gotten in a muddle here , but pkgtool gave an error that packages files should end in .tgz
Note that not all .tgz tarballs are the same. The ones for Slackware include some standardized script files that the Slackware package installer runs to configure things for you. When these scripts don't exist, you have to do any configuring yourself.
Originally posted by chr15t0 I just converted to Slack I like the idea of never having to use rmps again and doing everything from source.. but I just noticed that pkgtool needs .tgz files to install from.... but most source downloads that I have come across are as tar.gz . What is .tgz ? Please excuse my ignorance on this one...
The extension .tgz or .tar.gz doesn't necessarily mean that that has source code in it. This is just the type of package format that slackware uses to install packages (programs, libraries, etc).
When I want to install something new, I usually go out to sourceforge or freshmeat and download a zipped tar file, tar.gz which includes all the install scripts and readmes and the source.. all in one tidy little bundle. I extract with tar -zxvf, then cd into the new folder and then
Now, my understanding is that pkgtool will manage this process for me and keep a record of my installations, allowing me to keep a track of what I have installed on the system, checking dependencies as I come to install new packages.
I had a fiddle with this yesterday, loaded pkgtool, selected to install a new package and offered the tar.gz bundle for the application I wanted to install (in this case it was Grip). The system responded, saying that it was expecting a .tgz file and not a tar.gz. My understanding is that the only difference is in the name and not the format... hmm I guess I should go and read some more on pkgtool
Thanks for the help, guys
btw, having switched over to Slack from RedHat, I have to say I'm pretty impressed so far with the simplicity of things... I think I'm gonna like this!
Slackware and pkgtool use the .tgz extension for precompiled slackware binary packages, if you want to make a slackware package from source have a look at makepkg and to open up a slackware package look at explodepkg
Wonderful thread here. I read the above link about making pakages for Slackware. Also very helpful. Here is what I'm not sure about. I want to install Opera 6.03 onto my computer. However the ./configure --prefix=/slackpacks does not work. To install the version of software ./install.sh which will install it system wide. This is fine but I would rather do it via installpkg so I can easily remove all of it at a later date if I need too. Any suggestions on how I build this. Also if I downloaded the tar.gz and did tar zxvf file does this mean I now have the binary files or just the source files? One last thing, there is a file called runme.sh which if executed will run Opera. So I'm guessing (and hoping) I can just do a makepkg foo.tgz while I'm in the dir with this file?
Last edited by enzo250gto; 09-03-2002 at 12:03 AM.
This program is a miracle solution that you may like as well. Basically, when you have package source you compile yourself and want to install, here are the steps I follow:
the checkinstall command basically runs "make install" for you, and then builds a slackware package for you, and then installs that package using pkgtool. You can optionally pass it any required paramters as well. You can even install binary only stuff using checkinstall. It is really a great program that I hope gets added to slackware some day.
Go for the CheckInstall program. I've hacked up my system by partial installs and removals and moving things that the precompiled slackware packages don't seem to work. But using CheckInstall I have a package that the package tool can remove.