diff options
| author | adam <adam@pkgsrc.org> | 2014-05-27 06:31:28 +0000 |
|---|---|---|
| committer | adam <adam@pkgsrc.org> | 2014-05-27 06:31:28 +0000 |
| commit | 0853d26aeb106eb519f24ebe6972c830ef7336d0 (patch) | |
| tree | 7ee996fcaf13467ac3966d869c96cd276314fbe1 /textproc | |
| parent | 693076730eec521b6143c202ae693ce11ef830c0 (diff) | |
| download | pkgsrc-0853d26aeb106eb519f24ebe6972c830ef7336d0.tar.gz | |
Changes 2.19:
** Improvements
Performance has improved, typically by 10% and in some cases by a
factor of 200. However, performance of grep -P in UTF-8 locales has
gotten worse as part of the fix for the crashes mentioned below.
** Bug fixes
grep no longer mishandles patterns like [a-[.z.]], and no longer
mishandles patterns like [^a] in locales that have multicharacter
collating sequences so that [^a] can match a string of two characters.
grep no longer mishandles an empty pattern at the end of a pattern list.
[bug introduced in grep-2.5]
grep -C NUM now outputs separators consistently even when NUM is zero,
and similarly for grep -A NUM and grep -B NUM.
[bug present since "the beginning"]
grep -f no longer mishandles patterns containing NUL bytes.
[bug introduced in grep-2.11]
Plain grep, grep -E, and grep -F now treat encoding errors in patterns
the same way the GNU regular expression matcher treats them, with respect
to whether the errors can match parts of multibyte characters in data.
[bug present since "the beginning"]
grep -w no longer mishandles a potential match adjacent to a letter that
takes up two or more bytes in a multibyte encoding.
Similarly, the patterns '\<', '\>', '\b', and '\B' no longer
mishandle word-boundary matches in multibyte locales.
[bug present since "the beginning"]
grep -P now reports an error and exits when given invalid UTF-8 data.
Previously it was unreliable, and sometimes crashed or looped.
[bug introduced in grep-2.16]
grep -P now works with -w and -x and backreferences. Before,
echo aa|grep -Pw '(.)\1' would fail to match, yet
echo aa|grep -Pw '(.)\2' would match.
grep -Pw now works like grep -w in that the matched string has to be
preceded and followed by non-word components or the beginning and end
of the line (as opposed to word boundaries before). Before, this
echo a@@a| grep -Pw @@ would match, yet this
echo a@@a| grep -w @@ would not. Now, they both fail to match,
per the documentation on how grep's -w works.
grep -i no longer mishandles patterns containing titlecase characters.
For example, in a locale containing the titlecase character
'Lj' (U+01C8 LATIN CAPITAL LETTER L WITH SMALL LETTER J),
'grep -i Lj' now matches both 'LJ' (U+01C7 LATIN CAPITAL LETTER LJ)
and 'lj' (U+01C9 LATIN SMALL LETTER LJ).
Diffstat (limited to 'textproc')
| -rw-r--r-- | textproc/grep/Makefile | 4 | ||||
| -rw-r--r-- | textproc/grep/distinfo | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/textproc/grep/Makefile b/textproc/grep/Makefile index 2abf58c8f49..49da22a8d7a 100644 --- a/textproc/grep/Makefile +++ b/textproc/grep/Makefile @@ -1,6 +1,6 @@ -# $NetBSD: Makefile,v 1.38 2014/02/23 15:30:31 adam Exp $ +# $NetBSD: Makefile,v 1.39 2014/05/27 06:31:28 adam Exp $ -DISTNAME= grep-2.18 +DISTNAME= grep-2.19 CATEGORIES= textproc MASTER_SITES= ${MASTER_SITE_GNU:=grep/} EXTRACT_SUFX= .tar.xz diff --git a/textproc/grep/distinfo b/textproc/grep/distinfo index 5bfc630901c..47609ebe430 100644 --- a/textproc/grep/distinfo +++ b/textproc/grep/distinfo @@ -1,5 +1,5 @@ -$NetBSD: distinfo,v 1.14 2014/02/23 15:30:31 adam Exp $ +$NetBSD: distinfo,v 1.15 2014/05/27 06:31:28 adam Exp $ -SHA1 (grep-2.18.tar.xz) = fdb12580714966745635da7d9db55060f88db28b -RMD160 (grep-2.18.tar.xz) = ceab2b128640718e73616863e9c506c9666517d6 -Size (grep-2.18.tar.xz) = 1213220 bytes +SHA1 (grep-2.19.tar.xz) = f491d4ad903ecd80b46c5e8cbf2e92f0f7652922 +RMD160 (grep-2.19.tar.xz) = a5f8c03b92dd7313ddbd55764e0d87eff67decac +Size (grep-2.19.tar.xz) = 1234676 bytes |