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.
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.
the extention means the same thing; they are both "tar balls"
It may help to say that there is nothing about a .tgz suffixed file that implies a slackware package. It's just a gzip compressed tar file making it synonymous with .tar.gz
What makes a given .tgz a slackware package is the context of the contents of that archive. Therefore making some arbitrary .tar.gz suffixed file a slackware package is not merly a matter of some simple conversion, it is a matter of correctly constructing a package using some data that _may_ be in a .tar.gz file.
gbonvehi cites a good place to learn about package construction if that's really what you want to do. But the conversion between tar.gz distributed source and a slackware package isn't some one step command.
I was reading over this post and thinking "what's the quickest way to recognise that it's a tar.gz or a slackware package (tgz)?". Probably it would be that
A tar.gz (source files) ...
1) has text files called README, INSTALL with info on compilation (but tgz may have these too)
2) has Makefile or some text files that mention make, or perhaps a setup script like setup.pl
2) has a autogen.sh or configure script used to start off the package making routine
3) has a src/, doc/ or lib/ directory but not usually a bin/ directory
A tgz usually has just a couple of directories in the root of the file and they usually correspnd to high level system dir such as usr, share. A tgz also usually has an install/ dir with a doinst.sh file.
Well, then it is little more complicated to build a Slackwarepackage from a sourcepackage.
Very confusing to have Slackwarepackages named after tarball's.
How so? This is exactly what it is. A Slackware package is just a tarball of install files. If you wanted to, you can install a Slackware package by simply untarring it to the root directory (Infact this is how I installed pkgtools in Knoppix so I could install the downloaded Slackware packages to a mounted partition).
In my opinion, you couldn't find a better package management system.