How to convert a tar.gz-file to tgz-file ?
 

Hi !

How do I convert a tar.gz-file to tgz-file ?

I use Slackware 10.0.

Thanks !

the extention means the same thing; they are both "tar balls"

It's the same
 

Though I'm not so sure if that's what you meant... or are you trying to build your own tgz packages?

I've dowloaded a tar.gz-file and want's to have it in the .tgz-format instead.

Thats all ....

I want a Slackware pack ...

How do build a tgz-file from a tar.gz-file then ?

if you want to build a slackware package you need to do the following..

You may want to read a bit more about Slackware packages before trying to make them, a good starting point: http://www.linuxpackages.net/howto.php
Examining existing packages is a good learning experience too.
There's a little tool created by gnashley that can help you to compile programs easily and make packages from them, make a search on this forum, there's a thread about it ( http://www.linuxquestions.org/questi...d.php?t=462649 ).

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.

and you can look for those directories with "tar -tzf filename.tgz|less"

or simply "less filename.tgz"

OK !!! :scratch:

Thank you all very much for the information.

Well, then it is little more complicated to build a Slackwarepackage from a sourcepackage.

Very confusing to have Slackwarepackages named after tarball's.

Thanks !
Philip

You can always get a bunch of Slackware ready-to-install packages at http://www.linuxpackages.net/

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.

regards,
...drkstr

**edit**
my 1000'th post. Neato!

Don't forget to manually run the doinst.sh script and clean up the /install directory if you go that route. :)

That's a cool trick. Thanks!