public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: grep 3.8 - promotion to current stable
Date: Fri, 4 Nov 2022 13:07:11 -0600	[thread overview]
Message-ID: <cde96c9e-fafc-769d-d6a3-4375ed5fb1d6@SystematicSw.ab.ca> (raw)
In-Reply-To: <87fsezx534.fsf@Rainer.invalid>

On Thu, 03 Nov 2022 19:31:27 +0100, 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.

The issue does not appear to be about POSIX compliance, but that [ef]grep were 
dropped from POSIX before 2008 and declared obsolescent, so the maintainers 
appear to be looking to drop those commands/scripts.

You could perhaps reach out to Eric Blake or Jim Meyering who are in the GNU 
grep contributor lists for rationale.

While Debian and OpenSuSE have reverted that change, Fedora has not in main or 
rawhide.

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

  parent reply	other threads:[~2022-11-04 19:07 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
2022-11-04 19:07             ` Brian Inglis [this message]
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=cde96c9e-fafc-769d-d6a3-4375ed5fb1d6@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).