Prev: HAL\udev from the command line or a bash script?
Next: microphone and skype on dell latitude 2100
From: Dan C on 12 Feb 2010 16:54 On Fri, 12 Feb 2010 13:11:31 -0800, Keith Keller wrote: > 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. I see. I hadn't realized that 'xz' was a standalone program and that tar piped to it when used with pkgtools. Thanks for the clarification. -- "Ubuntu" -- an African word, meaning "Slackware is too hard for me". "Bother!" said Pooh, as Lorena Bobbitt tied him to the bed. Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/ Thanks, Obama: http://brandybuck.site40.net/pics/obama_thanks.jpg
From: Richard Herbert on 12 Feb 2010 21:51 On Thu, 11 Feb 2010 21:11:53 -0800, allend wrote: > You can also use Midnight Commander. Highlight the *.txz and hit F3 > (View). Thanks. I should have thought of that! Of course, I was using the 12.2 version of MC, but I just grabbed the "current" version, and it works like a charm. Thanks very much for all of the other helpful suggestions. Richard Herbert
From: Eef Hartman on 22 Feb 2010 05:36 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). As long as the xz program itself is available you can use the --use-compress-program=xz option with any older version of tar (instead of the "-z" or "-j" ones) and it will work fine. Have been using this a long time in both 10.2 and 12.2 releases and even Pat's own tar-1.13 will do this (it is not the way HE does it, but it does work, see this from its usage screen: --use-compress-program=PROG filter through PROG (must accept -d) -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
From: Eef Hartman on 22 Feb 2010 05:39 Dan C <youmustbejoking(a)lan.invalid> wrote: > On Fri, 12 Feb 2010 10:59:35 -0800, Keith Keller 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...? Maybe the fact that Pat is NOT using that tar version? <grin> The pkg toolsset a long time has been using tar 1.13 exclusively as never versions seem to conflict with the way these scripts work. -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
First
|
Prev
|
Pages: 1 2 3 4 Prev: HAL\udev from the command line or a bash script? Next: microphone and skype on dell latitude 2100 |