From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: grep 3.8 - promotion to current stable
Date: Fri, 4 Nov 2022 13:47:58 +0100 [thread overview]
Message-ID: <Y2UJ/jQebc/hijh9@calimero.vinschen.de> (raw)
In-Reply-To: <87fsezx534.fsf@Rainer.invalid>
On Nov 3 19:31, Achim Gratz wrote:
> Brian Inglis writes:
> > Suggest that I could come up with a package grep-nowarn which can only
> > suppress the [ef]grep warnings, where the package would install
> > [ef]grep-nowarn, and the postinstall script could rename the
> > distributed shell scripts to [ef]grep-warn, and install alternatives
> > with -warn priority 10, -nowarn priority 20; preremove would reverse
> > the process.
> >
> > Suggestions to accommodate -nowarn from grep package postinstall?
> > I could supply the same postinstall and preremove as -nowarn to check
> > for -nowarn and install or uninstall the alternative.
> >
> > Sequence or timing issues to watch out for during postinstall/preremove?
>
> As Corinna already said, why GNU suddenly cares so much about strict
> POSIX conformance in this case is puzzling. If anything they should
> have left the decision to packagers and IMNHO the warning should only be
> presented when POSIXLY_CORRECT is set in the environment, if at all.
> The patch to the wrapper script(s) in question is trivial and several
> Linux distributions have removed the warning already (if you do this,
> also change the interpreter from bash to dash). Just skip any
> extra packages and do the same.
+1
Corinna
next prev parent reply other threads:[~2022-11-04 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20220904140803.17862-1-Brian.Inglis@SystematicSW.ab.ca>
2022-09-29 18:55 ` Brian Inglis
2022-10-27 16:25 ` Corinna Vinschen
2022-10-28 6:49 ` Brian Inglis
2022-10-28 8:13 ` Corinna Vinschen
2022-10-28 8:20 ` Corinna Vinschen
2022-10-28 13:36 ` Thomas Wolff
2022-11-19 20:26 ` Brian Inglis
2022-10-28 12:40 ` gs-cygwin.com
2022-10-28 14:29 ` Corinna Vinschen
2022-11-03 18:08 ` Brian Inglis
2022-11-03 18:31 ` Achim Gratz
2022-11-04 0:09 ` Richard H. Gumpertz
2022-11-04 12:47 ` Corinna Vinschen [this message]
2022-11-04 19:07 ` Brian Inglis
2022-11-04 19:27 ` Corinna Vinschen
2022-11-13 17:09 ` Thomas Wolff
2022-11-13 22:13 ` Brian Inglis
2022-11-14 5:21 ` Thomas Wolff
2022-11-13 21:06 Brian Inglis
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=Y2UJ/jQebc/hijh9@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/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).