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: Wed, 26 Sep 2007 10:14:58 +0200	[thread overview]
Message-ID: <2021306.3IsArpDem0@kn.gn.rtr.message-center.info> (raw)
In-Reply-To: 20070926081837.3d5c2310@krikkit.digimed.co.uk

Neil Bothwick <neil@digimed.co.uk> wrote:

> Hello Alexander Skwar,
> 
>> Yes, it's very bad that Gentoo scripts don't limit themselves to
>> POSIX. Another windmill to fight against.
> 
> Artificially limiting yourself to the lowest common denominator when
> better options are available is bad, and discourages evolution.

Well, depends.

Making use of non standard options when standard compliant
options are avialable, is no-good evolution. It very much
tastes of the way Microsoft handles standards. Eg. have a
look at how MS treated Java or HTML (granted, Netscape wasn't
much better either).

Back to tar: Why use "tar -j" in scripts, when "bzip2 | tar"
does the same thing? I very much disagree that "tar -j" is
the "better" option here; in fact, I'd say that "bzip2 | tar"
is the better option, as it works on a lot more systems than
"tar -j" does. Heck, "tar -j" even does not work on all GNU
tar implementations, as very old GNU tars don't have bzip2
support at all and -j wasn't always used for bzip2.

> POSIX 
> specifies the minimum set of options and features, not the maximum. As
> long as the standards aren't broken, nothing is wrong, and adding new,
> useful and compatible features is one way that standards get improved.

No, it's not. To improve a standard, you make sure that the standard
gets amended and then you implement something. Not the other way around.

Alexander Skwar

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-09-26  8:29 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               ` [gentoo-user] " Alexander Skwar
2007-09-25 14:27                 ` Neil Bothwick
2007-09-26  7:01                   ` [gentoo-user] " Alexander Skwar
2007-09-26  7:18                     ` Neil Bothwick
2007-09-26  8:14                       ` Alexander Skwar [this message]
2007-09-26  8:35                         ` [gentoo-user] " 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=2021306.3IsArpDem0@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