From: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, ????????? <iyzsong@gmail.com>
Subject: Re: [PATCH] gnu: Add Wine.
Date: Sat, 15 Nov 2014 14:47:15 -0200 [thread overview]
Message-ID: <20141115144715.685fef84@freedom-laptop> (raw)
In-Reply-To: <20141115154815.GA4721@intra>
Em Sat, 15 Nov 2014 16:48:15 +0100
John Darrington <john@darrington.wattle.id.au> escreveu:
> As I understand it, it only even comes close, if the POSIXLY_CORRECT
> environment variable is set. Even then there are some differences.
I think you are right. However, they often use "POSIX-compliant"
loosely. Something that would be better described as "POSIX-like" or
"almost POSIX-compliant for our practical needs", or even
"Unix-like-like-the-one-we-used-to-build-and-run-our-code-successfully".
Absolute and strict compliance to a given standard, with almost
mathematical certainty, is something rather theoretical. I'm not an
expert, but I think that, even without 'POSIXLY_CORRECT' set, GNU
is a quite good "POSIX-compliant" OS in the vulgar sense, given that it
satisfies the majority of programs intended to run under
"POSIX-compliant" operating systems. And, IMHO, that's what they
usually mean.
--
,= ,-_-. =. Bruno Félix Rezende Ribeiro (oitofelix) [0x28D618AF]
((_/)o o(\_)) There is no system but GNU;
`-'(. .)`-' GNU Linux-Libre is one of its official kernels;
\_/ All software must be free as in freedom;
next prev parent reply other threads:[~2014-11-15 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 14:41 [PATCH] gnu: Add Wine 宋文武
2014-11-15 14:45 ` John Darrington
2014-11-15 15:05 ` Bruno Félix Rezende Ribeiro
2014-11-15 15:48 ` John Darrington
2014-11-15 16:47 ` Bruno Félix Rezende Ribeiro [this message]
2014-11-15 17:01 ` John Darrington
2014-11-15 15:10 ` 宋文武
2014-11-15 15:02 ` 宋文武
2014-11-15 18:15 ` Ludovic Courtès
2014-11-15 16:39 ` 宋文武
2014-11-15 18:21 ` Ludovic Courtès
2014-11-16 3:00 ` 宋文武
2014-11-16 17:27 ` Ludovic Courtès
2014-11-17 12:34 ` 宋文武
2014-11-17 13:30 ` Ludovic Courtès
2014-11-18 21:32 ` Ludovic Courtès
2014-11-19 11:38 ` 宋文武
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141115144715.685fef84@freedom-laptop \
--to=oitofelix@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).