-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Onion ponion@alien.bt.co.uk wrote:
On Fri, 2005-07-15 at 11:14 +0100, Chris Green wrote:
.tgz files can be Slackware packages which are packaged for automatic installation by Slackware's package system. They won't (in that case) include the source for building yourself.
.tgz is to Slackware what .rpm is to Red Hat (and other distributions).
That seems a very stoopid way to do things... I've always considered .tgz to be a short hand for .tar.gz i.e. a tar-ball compressed with gzip... Nothing more.. Nothing less.
I've never come across one that was specific to slackware though.
.tgz is the standard SlackWare packages format, it's been that way for years, you wouldn't have encountered it unless you'd used slackware, there *are* some .tgz files that are 'slackware specific', it's just that they are few and far between. And they're normally fairly well labelled as SlackWare packages.
It's not stoopid, the slackware packages *are* just binaries in a .tgz file, with a couple of scripts in there for setting stuff up nicely. It's no worse an idea than .rpm.
Personally, I've used SlackWare, it's a lovely distribution, but it's drawbacks (for me, when I was running it) where that the package management wasn't brilliant, and that if you did want something that was new, source *was* the way forwards.
Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk