-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Brett Parker iDunno@sommitrealweird.co.uk wrote:
Peter Onion ponion@alien.bt.co.uk wrote:
Ok, "stooppid" wassn't what I ment. It seems "Unhelpful" to use a non-unique extension in that way. Atleast ".rpm" tells you whats in there, which is afterall the purpose of the extension.
As a general rule of thumb, most people do not use .tgz to mean .tar.gz, and so I don't think it's particularly unhelpful. Most source distributions these days come with 3 different extensions...
.tar.gz - good ol' gzip'd tar archive .tar.bz2 - more recent player in the field, generally better compression than gzip, uses bzip2 to compress the tar archive. .zip - for the windows people that know no better!
I don't think that I've seen a .tgz file as a .tgz file for some time, but then I tend to use .deb files... and even then they're generally hidden behind apt! (Except the packages that I build, which then get moved in to the webtree, and are then apt-able too :)
OK - Erm, I should have qualified this further... I've not seen a *distributed* source tar ball as a .tgz file rather than a .tar.gz or .tar.bz2 file in quite some time... (bloody pedantic bunch on #alug at the moment... *winks* at quinophex and Paperface).
It was pointed out to me that pbuilder uses a .tgz file, but as pbuilder's .tgz file is actually basically a chroot, it's a binary package, so I don't think that really counts here... oh, and of course, that's not distributed, so also probably doesn't count.
Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk