public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/15831] Bad $expect passed from tst-fmon.sh to tst-fmon
Date: Sun, 18 Aug 2013 20:47:00 -0000	[thread overview]
Message-ID: <bug-15831-131-PxAUgIf7Do@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15831-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15831

--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 14 Aug 2013, carlos at redhat dot com wrote:

> There are patches outstanding to glibc to allow it to build with a POSIX shell
> and not require bash-specific extensions.
> 
> I suggest looking through back months in libc-alpha, finding the patches that
> were posted and adding them to the `Pending Reviews' list so we don't loose
> track of them and get around to reviewing them:
> http://sourceware.org/glibc/wiki/Pending%20Reviews
> 
> Note, you need to be in EditorGroup to edit the wiki:
> http://sourceware.org/glibc/wiki/EditorGroup
> 
> This would go a long way to fixing this problem.
> 
> At present we only support /bin/bash, thus closing as RESOLVED/INVALID.

I don't believe your answer justifies closing this bug, or is in any way 
relevant to this bug.  Such patches as there are are about making 
installed bash scripts such as ldd into installed POSIX shell scripts.  
They are not about supporting building or testing glibc without bash 
available for scripts that require bash.  And they are not about cases 
where scripts use /bin/sh but in fact require non-POSIX shell features - 
such cases are all bugs, for which two fixes are possible in each case 
(either explicitly require bash for the script, or make it work with the 
POSIX shell).

This script (tst-fmon.sh) is an sh script.  So, if it doesn't work with a 
POSIX shell, that's a bug, not an enhancement request, and not invalid, 
and should be fixed in one of those two ways.

Now, the analysis in this bug does not appear to disclose whether in fact 
the script is doing anything non-POSIX, or whether the problem comes from 
a dash bug where dash fails to follow POSIX requirements - if the latter, 
the bug would indeed be invalid.  But such an analysis of whether the 
differences between bash and dash reflect a dash bug or the script 
requiring something beyond POSIX is needed before the bug can be 
considered invalid.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-08-18 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 21:32 [Bug localedata/15831] New: " slicer_ghent at hushmail dot com
2013-08-12 22:55 ` [Bug localedata/15831] " schwab@linux-m68k.org
2013-08-14  3:46 ` slicer_ghent at hushmail dot com
2013-08-14 14:50 ` carlos at redhat dot com
2013-08-18 20:47 ` joseph at codesourcery dot com [this message]
2013-08-19 18:29 ` carlos at redhat dot com
2014-06-13 13:12 ` fweimer at redhat dot com

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=bug-15831-131-PxAUgIf7Do@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).