public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: star
Date: Tue, 25 Sep 2007 15:34:41 +0200	[thread overview]
Message-ID: <2734612.RV0q0BIfvm@kn.gn.rtr.message-center.info> (raw)
In-Reply-To: 46F90C23.20204@gmail.com

b.n. <brullonulla@gmail.com> wrote:

> Alexander Skwar ha scritto:
>> Stroller <stroller@stellar.eclipse.co.uk> wrote:
>> 
>>> On 24 Sep 2007, at 09:30, Alexander Skwar wrote:
>>>> ...
>>>>> and if p7zip supports pipes, you don't need its support in tar.
>>>>> Just pipe
>>>>> from/to it.
>>>> It does and that's the way it's supposed to be used on unix, according
>>>> to its manpage.
>>> GNU tar features the -j, -z and -Z options.
>> 
>> Yes, bad, isn't it? These options are not part of the Posix standard.
>> It would be good, if these superflous options wouldn't be present at
>> all. I say "superflous", as pipes work just fine.
> 
> It's not that an option becomes "bad" just because it's not carved into
> the POSIX standard.

To a degree, it is.

> What's important, I guess, is that tar is  
> POSIX-compliant, so that if you want, you can build POSIX-compliant
> scripts etc. ,

Depends. On the hand, you're right. But if non-compliant options
exist, people tend to use them. That's bad in so far, as they get
used to non-standard behaviour. That's especially bad, as standard
compliants solution exist.

> but I can't see how non-POSIX but handy extensions could 
> be bad. 

Let me give you a different example, although it has nothing
to do with POSIX.

Internet Explorer translates a \ in a URL to /. That's a non
standard compliant behaviour. Now, as many people (still *G*)
use IE, many people rely on that mis-behaviour of IE and make
it hard for non-misbehaving browsers (ie. Mozilla) to display
the content.

What does this have to do with GNU tar and it adding superflous
options? Quite a lot. -j et.al. are non-standard options. If a
(badly written) script relies on the presence of -j, this script
won't work with a POSIX compliant tar (like star or any Unix
tar (eg. Sun, HP, ...)). Is that bad? Yes, it is. It is bad, as
there's an easily accessible solution to this problem available:
Use pipes! In this case, the solution would be: 

        tar cf - dir | bzip2 > dir.tar.bz2
        tar cf - dir | 7z a -si dir.tar.7z

Or for decompression:

        bzcat dir.tar.bz2 | tar xf -
        7z x -so dir.tar.7z | tar xf -

> Maybe it's me not seeing the problem.

Yep.

> Maybe the POSIX standard  
> could just be extended as well. :)

Equally fine.

>>> and it would be nice to see p7zip supported
>>> in the same way.
>> 
>> No.
> 
> "No" means nothing. Tell us why.

Pipes exist. The current "integration" of 7-zip is fine. There's
no need to integrate other compression into tar. Actually, there's
no need at all to integrate ANY compression alg. into tar.

Furthermore, especially with 7zip, an integration into tar would
make the use of 7zip somewhat limited, as all of the additional
command line options of 7z would not be accessible anymore.

Alexander Skwar

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-09-25 14:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 16:03 [gentoo-user] star Florian Philipp
2007-09-22 17:23 ` Volker Armin Hemmann
2007-09-22 18:14   ` Florian Philipp
2007-09-22 20:00     ` Volker Armin Hemmann
2007-09-24  8:30       ` [gentoo-user] star Alexander Skwar
2007-09-24 17:58         ` Stroller
2007-09-25  6:22           ` [gentoo-user] " Alexander Skwar
2007-09-25 13:24             ` b.n.
2007-09-25 13:34               ` Alexander Skwar [this message]
2007-09-25 14:27                 ` [gentoo-user] " Neil Bothwick
2007-09-26  7:01                   ` [gentoo-user] " Alexander Skwar
2007-09-26  7:18                     ` Neil Bothwick
2007-09-26  8:14                       ` [gentoo-user] " Alexander Skwar
2007-09-26  8:35                         ` Neil Bothwick
2007-09-26  8:45                           ` [gentoo-user] " Alexander Skwar
2007-09-26  8:59                             ` Neil Bothwick
2007-09-26  9:49                               ` Bo Ørsted Andresen
2007-09-26 10:08                               ` [gentoo-user] " Alexander Skwar
2007-09-26 11:07                                 ` Neil Bothwick
2007-09-26 13:22                     ` [gentoo-user] " Volker Armin Hemmann
2007-09-24  8:27     ` [gentoo-user] " Alexander Skwar
2007-09-24 16:38       ` Florian Philipp
2007-09-25  6:27         ` [gentoo-user] " Alexander Skwar
2007-09-25 16:37           ` Florian Philipp
2007-09-25 20:58       ` [gentoo-user] " Michael Schreckenbauer
2007-09-25 22:26         ` b.n.
2007-09-26  9:45           ` Michael Schreckenbauer
2007-09-26 17:44             ` b.n.
2007-09-26 17:46               ` Neil Bothwick
2007-09-24  8:24 ` Alexander Skwar
2007-09-25 20:55 ` [gentoo-user] star Michael Schreckenbauer
     [not found] <46f98ceb.FK1zsMF7EsB2Kd3W%Joerg.Schilling@fokus.fraunhofer.de>
2007-09-26 17:52 ` [gentoo-user] star b.n.
  -- strict thread matches above, loose matches on Subject: below --
2007-09-28 14:43 Joerg Schilling
2007-09-28 17:56 ` Alexander Skwar
2007-09-28 19:52   ` Joerg Schilling
2007-09-28 14:55 Joerg Schilling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2734612.RV0q0BIfvm@kn.gn.rtr.message-center.info \
    --to=listen@alexander.skwar.name \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox