public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] POSIX shell and "portable"
Date: Mon, 05 Nov 2007 10:22:36 +0100	[thread overview]
Message-ID: <1194254556.6977.46.camel@sapc154> (raw)
In-Reply-To: <1194050878.16405.10.camel@uberpc.marples.name>

On Sat, 2007-11-03 at 00:47 +0000, Roy Marples wrote:

As it seems too few people really accept your suggestion, I feel it's
time for me to chime in too, although I don't know what exactly POSIX-sh
standard defines.

> On Sat, 2007-11-03 at 01:19 +0100, Fabian Groffen wrote:
> > On 02-11-2007 17:35:08 +0000, Roy Marples wrote:
> > > I don't see them as inferior.
> > > I see them as more portable and less confusing.
> > 
> > Please stop calling it "more portable".
> 
> But is it more portable as then then works across more than one shell.
> 
> >   The shell code you see in
> > configure can in a way be called "portable".  Your POSIX compliant stuff
> > isn't.
> 
> Sure it is - it should work on a shell that claims POSIX compliance.
> 
> >   In fact, by stating #!/bin/sh you actually make the code useless
> > on a number of platforms, where it would have been working fine if there
> > just were #!/bin/bash there.
> 
> Then the issue is to fix their sh so it follows POSIX compliance.
> As soon as a dash, bb or FreeBSD sh issue is found where it deviates
> from POSIX but it works on bash a lot of people say "dash bug, therefore
> invalid

Agreed, but (speaking for alt/prefix):

Alt/prefix is designed to (mainly) work without superuser access on the
target machine, which may also be Solaris, AIX, HP-UX and the like.
/bin/sh on such a machine is not POSIX-shell, but old bourne-shell
(unfortunately with bugs often).
And it is _impossible_ to have sysadmins to get /bin/sh a POSIX-Shell
nor to have that bugs fixed.

But yes, on most machines there is /bin/ksh, which IMHO is POSIX
compliant (maybe also with non-fixable bugs).

Although I do not know yet for which _installed_ scripts it'd be really
useful to have them non-bash in alt/prefix, I appreciate the discussion.

To see benefits for alt/prefix too, it _might_ require that discussion
going from requiring /bin/sh being POSIX-sh towards being
bourne-shell...

> 
> > It seems to me that you actually mean "more FreeBSD-able" or something,
> > which is a high price to pay for a relatively small part of Gentoo as a
> > whole.
> 
> More embeddable.
> More BSDable.
> More Linuxable - bash isn't the only linux shell, there are plently of
> others.

More (generic) unix-able.

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-11-05  9:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 13:44 [gentoo-dev] More general interface to use flags Marijn Schouten (hkBst)
2007-11-02 14:04 ` Roy Marples
2007-11-02 14:27   ` Marijn Schouten (hkBst)
2007-11-02 14:52     ` Roy Marples
2007-11-02 14:59   ` Mike Frysinger
2007-11-02 15:30     ` Roy Marples
2007-11-02 15:38       ` Mike Frysinger
2007-11-02 15:48         ` Roy Marples
2007-11-02 15:58           ` Mike Frysinger
2007-11-02 16:10             ` Roy Marples
2007-11-02 16:30               ` Bo Ørsted Andresen
2007-11-02 16:52                 ` Roy Marples
2007-11-02 17:17                   ` Bo Ørsted Andresen
2007-11-02 17:35                     ` Roy Marples
2007-11-03  0:19                       ` [gentoo-dev] POSIX shell and "portable" Fabian Groffen
2007-11-03  0:47                         ` Roy Marples
2007-11-05  9:22                           ` Michael Haubenwallner [this message]
2007-11-05 10:13                             ` Roy Marples
2007-11-05 13:21                               ` Michael Haubenwallner
2007-11-05 20:21                                 ` Mike Frysinger
2007-11-05 23:18                                   ` Roy Marples
2007-11-06  7:12                                     ` Ciaran McCreesh
2007-11-06  7:40                                       ` Roy Marples
2007-11-06  8:03                                         ` Ciaran McCreesh
2007-11-06  8:25                                           ` Roy Marples
2007-11-06  9:04                                     ` Michael Haubenwallner
2007-11-05 20:32                                 ` Roy Marples
2007-11-05 20:55                                   ` Fabian Groffen
2007-11-05 22:27                                   ` Mike Frysinger
2007-11-03  0:57                         ` Natanael copa
2007-11-03  1:06                         ` Roy Marples
2007-11-03 16:19                           ` [gentoo-dev] " Steve Long
2007-11-03  1:10                         ` [gentoo-dev] " Roy Marples
     [not found]                       ` <b41005390711022225i4f30bb01jbf5a040c60c4b088@mail.gmail.com>
2007-11-03  5:26                         ` Fwd: [gentoo-dev] More general interface to use flags Alec Warner
2007-11-03 21:57                           ` Mike Frysinger
2007-11-04 10:54 ` [gentoo-dev] " Steve Long
2007-11-04 21:54   ` Alec Warner
2007-11-06 11:50     ` Steve Long

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=1194254556.6977.46.camel@sapc154 \
    --to=haubi@gentoo.org \
    --cc=gentoo-dev@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