The attached patch shows my current work on adapting sltar
to sbase. It is functional, but, there are still open questions
regarding tar. The big deal is the argument parsing: I would
like to use the ARG macros in tar, but I'm not sure how that
fits with the average tar invocation.
In short, how
On Jul 6, 2013 12:16 PM, Galos, David galos...@students.rowan.edu wrote:
In short, how do you fine folks invoke your tar?
$ tar czf filename.tar.gz foldername
$ tar tzf filename.tar.gz
$ tar xzf filename.tar.gz
Dmitrij D. Czarkoff
tar xzf filename.tar.gz ~/scratch/
On 06/07/2013 8:20 PM, Dmitrij Czarkoff czark...@gmail.com wrote:
On Jul 6, 2013 12:16 PM, Galos, David galos...@students.rowan.edu
wrote:
In short, how do you fine folks invoke your tar?
$ tar czf filename.tar.gz foldername
$ tar tzf filename.tar.gz
$
Also
$ tar cjf file.tar.bz2 folder
$ tar cJf file.tar.xz folder
and
$ tar xf filename.tar.compression-suffix
On Sat, Jul 06, 2013 at 08:30:39PM +1000, Daniel Bryan wrote:
tar xzf filename.tar.gz ~/scratch/
On 06/07/2013 8:20 PM, Dmitrij Czarkoff czark...@gmail.com wrote:
On Jul 6, 2013
Apparently is there anybody who uses dashes in tar's keys?
Dmitrij D. Czarkoff
On 06/07/2013 8:30 PM, Daniel Bryan danbr...@gmail.com wrote:
tar xzf filename.tar.gz ~/scratch/
Sorry, this should have been:
tar xzf filename.tar.gz -C ~/scratch/
On 2013-07-06 10:52, Adam Brand wrote:
The problem ended up being that the Terminus font wasn't installed. Maybe a
good add to the requirements for install (xfonts-terminus)?
There is no requirements file, what do you mean? If you are talking about
package dependencies, the package has nothing
On Sat, 6 Jul 2013 10:59:36 -0400 Alex Pilon a...@alexpilon.ca wrote:
On Sat, Jul 06, 2013 at 01:29:02PM +0200, Dmitrij Czarkoff wrote:
Apparently is there anybody who uses dashes in tar's keys?
Yeah. Old habit.
I also see it a lot in scripts, along with using full options instead
of
On Jul 6, 2013 5:04 PM, Andrew Hills ahi...@ednos.net wrote:
So, for compatibility, perhaps it is best to allow both.
You mean the whole lot of GNU tar long options including filename rewriting
and masks? I don't see any way such implementation could fit suckless
principles.
I would suggest a
On 2013-07-06, at 12:15, David Galos wrote:
In short, how do you fine folks invoke your tar?
My habit relays on compression scheme detection:
tar cf foo.txz ~/stuff
tar xf bar.tbz
-Truls
I would suggest a subset of POSIX tar options. It could be possibly
amended with z, Z, j and J options, though using
A $ tar c dirname | gzip -9c filename.tar.gz
or
A $ tar cf - dirname | gzip -9c filename.tar.gz
I usually use:
gunzip file.tar.gz | tar xf
Greetings.
In afgets() the size variable is never updated, which usually means it is always
zero, in which case it has no purpose at all. I believe it is supposed to be
updated on realloc? This way, calling afgets multiple times with the same
arguments will reuse the space if possible.
Also, the
I also see it a lot in scripts, along with using full options instead
of short--perhaps to be more verbose? So, for compatibility, perhaps it
is best to allow both.
If you mean GNU --long-options, then never in a million years :) If
you mean both dashed and non, that is likely what I will do.
13 matches
Mail list logo
