Prev: HAL\udev from the command line or a bash script?
Next: microphone and skype on dell latitude 2100
From: Jim Diamond on 12 Feb 2010 11:55
On 2010-02-12 at 11:49 AST, Keith Keller <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote:
> On 2010-02-12, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
>>
>> tar -tvf filename.tar.gz
>>
>> to look at its contents. I don't know if some extra switch is needed for
>> .txz files, but if tar is able to unpack with -x it should also be able to
>> view the contents with -t.
>
> I don't believe any version of tar that comes with Slackware supports xz
> compression, so you need to do something like the xzcat pipe I posted
> earlier (or the equivalent, like uncompressing the tarball on disk).

A two second experiment shows that /usr/bin/tar on Slack 13.0 happily
deals with .txz files. But if by "Slackware" you meant "older
versions of Slackware" I suspect you are right.

Cheers.
Jim
From: Keith Keller on 12 Feb 2010 13:59
On 2010-02-12, Jim Diamond <Jim.Diamond(a)nospam.AcadiaU.ca> wrote:
> On 2010-02-12 at 11:49 AST, Keith Keller <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote:
>>
>> I don't believe any version of tar that comes with Slackware supports xz
>> compression, so you need to do something like the xzcat pipe I posted
>> earlier (or the equivalent, like uncompressing the tarball on disk).
>
> A two second experiment shows that /usr/bin/tar on Slack 13.0 happily
> deals with .txz files. But if by "Slackware" you meant "older
> versions of Slackware" I suspect you are right.

Nice one! I just checked the man page (I have -current right before
13.0 was released), and there was nothing in there, but I should have
remembered that the man pages for GNU programs often suck.

tar -? shows that -J is the switch for xz compression (or --xz).

--keith

--
kkeller-usenet(a)wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

From: Dan C on 12 Feb 2010 14:59
On Fri, 12 Feb 2010 10:59:35 -0800, Keith Keller wrote:

> On 2010-02-12, Jim Diamond <Jim.Diamond(a)nospam.AcadiaU.ca> wrote:
>> On 2010-02-12 at 11:49 AST, Keith Keller
>> <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote:
>>>
>>> I don't believe any version of tar that comes with Slackware supports
>>> xz compression, so you need to do something like the xzcat pipe I
>>> posted earlier (or the equivalent, like uncompressing the tarball on
>>> disk).
>>
>> A two second experiment shows that /usr/bin/tar on Slack 13.0 happily
>> deals with .txz files. But if by "Slackware" you meant "older versions
>> of Slackware" I suspect you are right.
>
> Nice one! I just checked the man page (I have -current right before
> 13.0 was released), and there was nothing in there, but I should have
> remembered that the man pages for GNU programs often suck.
>
> tar -? shows that -J is the switch for xz compression (or --xz).

Why would one think that the version of tar which ships with Slack13
would *NOT* handle .txz files.... since that is the default package
compression method as of Slack13...?

</confused>


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he strafed the lifeboats.

Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/obama_thanks.jpg
From: Chick Tower on 12 Feb 2010 15:27
On 2010-02-12, Richard Herbert <rherbert(a)sympatico.ca> wrote:
> I'm still running Slackware 12.2, but I've had pretty good luck so far
> installing selected *.txz packages from Slackware 13. Is there a viewer
> for txz packages available?

If you want a permanent, easy-to-use solution, you should be able to modify
Midnight Commander to do the job. It can already read .tgz packages. You
can find out how to do it without modifying mc's source code in
/usr/share/mc/extfs, and I suspect modifying sfs.ini (if it exists in 12.2;
it doesn't seem to in 13.0, but it does in 12.0) will do the trick.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
From: Keith Keller on 12 Feb 2010 16:11
On 2010-02-12, Dan C <youmustbejoking(a)lan.invalid> wrote:
>
> Why would one think that the version of tar which ships with Slack13
> would *NOT* handle .txz files.... since that is the default package
> compression method as of Slack13...?

Well, partly because it doesn't. Remember that pkgtools uses tar-1.13
by default, which as far as I can tell does not support xz. So you see
this, for example, in installpkg:

( cd $ROOT/ ; $packagecompression -dc | $TAR -xlUpvf - ) < $package >>
$TMP/$shortname 2> /dev/null

where $packagecompression is determined by the extension.

As pkgtools demonstrates, it doesn't really matter what compression tar
supports, as long as an uncompression utility exists that can pipe to
stdout. Alternatively, tar can support arbitrary compression algorithms
through the -I switch.

--keith


--
kkeller-usenet(a)wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: HAL\udev from the command line or a bash script?
Next: microphone and skype on dell latitude 2100