DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 99ABF3858D1E
To: cygwin AT cygwin DOT com
Date: Sat, 27 May 2023 23:48:53 -0600
Message-Id: <announce.20230527234853.45767-1-Brian.Inglis@Shaw.ca>
Subject: [ANNOUNCEMENT] Upgraded: grep 3.11
From: Cygwin grep Co-Maintainer via Cygwin-announce via Cygwin
 <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Cygwin grep Co-Maintainer via Cygwin-announce <cygwin-announce AT cygwin DOT com>,
        Cygwin grep Co-Maintainer <Brian DOT Inglis AT Shaw DOT ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

The following package has been upgraded in the Cygwin distribution:

* grep	3.11

GNU grep searches one or more input files for lines containing a match
to a specified pattern. By default, grep outputs the matching lines. The
GNU implementation includes several useful extensions over POSIX.

This release makes PCRE patterns like [\d] work again, at the expense of
reverting to the behavior of grep 3.8, in that patterns like \w and \b
go back to using ASCII rather than Unicode interpretations.

Previous releases stated that egrep and fgrep are deprecated obsolescent
commands, will be dropped in future, and from this release until then,
every use will show a stderr warning message, reminding you how to
change your commands and scripts:

	$ egrep ...
	egrep: warning: egrep is obsolescent; using grep -E
	...
	$ fgrep ...
	fgrep: warning: fgrep is obsolescent; using grep -F
	...

Cygwin releases will suppress the egrep and fgrep warning messages, but
developers and maintainers should rigorously remove all such usages from
their practices and scripts, as those commands could be dropped, or any
warning messages could be treated as fatal errors, in future.

Other invalid usages documented previously also now generate stderr
warning or error messages e.g.

	grep: warning: * at start of expression
	grep: warning: ? at start of expression
	grep: warning: + at start of expression
	grep: warning: {...} at start of expression
	grep: warning: stray \ before <CHAR>
	grep: warning: stray \ before unprintable character
	grep: warning: stray \ before white space

For more information see the project home pages:

	https://www.gnu.org/software/grep/
	https://sv.gnu.org/projects/grep/

For changes since the previous Cygwin release, see below or read
/usr/share/doc/grep/NEWS after installation:

	https://lists.gnu.org/archive/html/info-gnu/2023-05/msg00004.html
	https://savannah.gnu.org/news/?id=10364

for complete details, read /usr/share/doc/grep/ChangeLog after
installation, or see:

	https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.11


Noteworthy changes in release 3.11	2023-05-13

Bug fixes

* With -P, patterns like [\d] now work again. Fixing this has caused
  grep to revert to the behavior of grep 3.8, in that patterns like \w
  and \b go back to using ASCII rather than Unicode interpretations.
  However, future versions of GNU grep and/or PCRE2 are likely to fix
  this and change the behavior of \w and \b back to Unicode again,
  without breaking [\d] as 3.10 did. [bug introduced in grep 3.10]

* grep no longer fails on files dated after the year 2038, when running
  on 32-bit x86 and ARM hosts using glibc 2.34+.
  [bug introduced in grep 3.9]

* grep -P no longer fails to match patterns using negated classes like
  \D or \W when linked with PCRE2 10.34 or newer.
  [bug introduced in grep 3.8]

Changes in behavior

* grep --version now prints a line describing the version of PCRE2 it
  uses. For example, it prints this when built with the very latest from
  git:
	grep -P uses PCRE2 10.43-DEV 2023-04-14

  or this with what's currently available in Fedora 37:

	grep -P uses PCRE2 10.40 2022-04-14

* previous versions of grep wouldn't respect the user provided settings
  for PCRE_CFLAGS and PCRE_LIBS when building if a libpcre2-8 pkg-config
  module was found.


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple