head 1.66; access; symbols pkgsrc-2023Q4:1.66.0.4 pkgsrc-2023Q4-base:1.66 pkgsrc-2023Q3:1.66.0.2 pkgsrc-2023Q3-base:1.66 pkgsrc-2023Q2:1.65.0.2 pkgsrc-2023Q2-base:1.65 pkgsrc-2023Q1:1.64.0.6 pkgsrc-2023Q1-base:1.64 pkgsrc-2022Q4:1.64.0.4 pkgsrc-2022Q4-base:1.64 pkgsrc-2022Q3:1.64.0.2 pkgsrc-2022Q3-base:1.64 pkgsrc-2022Q2:1.62.0.8 pkgsrc-2022Q2-base:1.62 pkgsrc-2022Q1:1.62.0.6 pkgsrc-2022Q1-base:1.62 pkgsrc-2021Q4:1.62.0.4 pkgsrc-2021Q4-base:1.62 pkgsrc-2021Q3:1.62.0.2 pkgsrc-2021Q3-base:1.62 pkgsrc-2021Q2:1.61.0.2 pkgsrc-2021Q2-base:1.61 pkgsrc-2021Q1:1.60.0.4 pkgsrc-2021Q1-base:1.60 pkgsrc-2020Q4:1.60.0.2 pkgsrc-2020Q4-base:1.60 pkgsrc-2020Q3:1.59.0.2 pkgsrc-2020Q3-base:1.59 pkgsrc-2020Q2:1.58.0.2 pkgsrc-2020Q2-base:1.58 pkgsrc-2020Q1:1.57.0.2 pkgsrc-2020Q1-base:1.57 pkgsrc-2019Q4:1.57.0.4 pkgsrc-2019Q4-base:1.57 pkgsrc-2019Q3:1.55.0.2 pkgsrc-2019Q3-base:1.55 pkgsrc-2019Q2:1.54.0.2 pkgsrc-2019Q2-base:1.54 pkgsrc-2019Q1:1.53.0.6 pkgsrc-2019Q1-base:1.53 pkgsrc-2018Q4:1.53.0.4 pkgsrc-2018Q4-base:1.53 pkgsrc-2018Q3:1.53.0.2 pkgsrc-2018Q3-base:1.53 pkgsrc-2018Q2:1.52.0.4 pkgsrc-2018Q2-base:1.52 pkgsrc-2018Q1:1.52.0.2 pkgsrc-2018Q1-base:1.52 pkgsrc-2017Q4:1.51.0.6 pkgsrc-2017Q4-base:1.51 pkgsrc-2017Q3:1.51.0.4 pkgsrc-2017Q3-base:1.51 pkgsrc-2017Q2:1.50.0.2 pkgsrc-2017Q2-base:1.50 pkgsrc-2017Q1:1.48.0.2 pkgsrc-2017Q1-base:1.48 pkgsrc-2016Q4:1.47.0.4 pkgsrc-2016Q4-base:1.47 pkgsrc-2016Q3:1.47.0.2 pkgsrc-2016Q3-base:1.47 pkgsrc-2016Q2:1.46.0.4 pkgsrc-2016Q2-base:1.46 pkgsrc-2016Q1:1.46.0.2 pkgsrc-2016Q1-base:1.46 pkgsrc-2015Q4:1.44.0.2 pkgsrc-2015Q4-base:1.44 pkgsrc-2015Q3:1.43.0.4 pkgsrc-2015Q3-base:1.43 pkgsrc-2015Q2:1.43.0.2 pkgsrc-2015Q2-base:1.43 pkgsrc-2015Q1:1.42.0.4 pkgsrc-2015Q1-base:1.42 pkgsrc-2014Q4:1.42.0.2 pkgsrc-2014Q4-base:1.42 pkgsrc-2014Q3:1.41.0.2 pkgsrc-2014Q3-base:1.41 pkgsrc-2014Q2:1.40.0.2 pkgsrc-2014Q2-base:1.40 pkgsrc-2014Q1:1.38.0.2 pkgsrc-2014Q1-base:1.38 pkgsrc-2013Q4:1.36.0.2 pkgsrc-2013Q4-base:1.36 pkgsrc-2013Q3:1.35.0.4 pkgsrc-2013Q3-base:1.35 pkgsrc-2013Q2:1.35.0.2 pkgsrc-2013Q2-base:1.35 pkgsrc-2013Q1:1.34.0.4 pkgsrc-2013Q1-base:1.34 pkgsrc-2012Q4:1.34.0.2 pkgsrc-2012Q4-base:1.34 pkgsrc-2012Q3:1.29.0.2 pkgsrc-2012Q3-base:1.29 pkgsrc-2012Q2:1.27.0.2 pkgsrc-2012Q2-base:1.27 pkgsrc-2012Q1:1.25.0.8 pkgsrc-2012Q1-base:1.25 pkgsrc-2011Q4:1.25.0.6 pkgsrc-2011Q4-base:1.25 pkgsrc-2011Q3:1.25.0.4 pkgsrc-2011Q3-base:1.25 pkgsrc-2011Q2:1.25.0.2 pkgsrc-2011Q2-base:1.25 pkgsrc-2011Q1:1.24.0.30 pkgsrc-2011Q1-base:1.24 pkgsrc-2010Q4:1.24.0.28 pkgsrc-2010Q4-base:1.24 pkgsrc-2010Q3:1.24.0.26 pkgsrc-2010Q3-base:1.24 pkgsrc-2010Q2:1.24.0.24 pkgsrc-2010Q2-base:1.24 pkgsrc-2010Q1:1.24.0.22 pkgsrc-2010Q1-base:1.24 pkgsrc-2009Q4:1.24.0.20 pkgsrc-2009Q4-base:1.24 pkgsrc-2009Q3:1.24.0.18 pkgsrc-2009Q3-base:1.24 pkgsrc-2009Q2:1.24.0.16 pkgsrc-2009Q2-base:1.24 pkgsrc-2009Q1:1.24.0.14 pkgsrc-2009Q1-base:1.24 pkgsrc-2008Q4:1.24.0.12 pkgsrc-2008Q4-base:1.24 pkgsrc-2008Q3:1.24.0.10 pkgsrc-2008Q3-base:1.24 cube-native-xorg:1.24.0.8 cube-native-xorg-base:1.24 pkgsrc-2008Q2:1.24.0.6 pkgsrc-2008Q2-base:1.24 cwrapper:1.24.0.4 pkgsrc-2008Q1:1.24.0.2 pkgsrc-2008Q1-base:1.24 pkgsrc-2007Q4:1.23.0.14 pkgsrc-2007Q4-base:1.23 pkgsrc-2007Q3:1.23.0.12 pkgsrc-2007Q3-base:1.23 pkgsrc-2007Q2:1.23.0.10 pkgsrc-2007Q2-base:1.23 pkgsrc-2007Q1:1.23.0.8 pkgsrc-2007Q1-base:1.23 pkgsrc-2006Q4:1.23.0.6 pkgsrc-2006Q4-base:1.23 pkgsrc-2006Q3:1.23.0.4 pkgsrc-2006Q3-base:1.23 pkgsrc-2006Q2:1.23.0.2 pkgsrc-2006Q2-base:1.23 pkgsrc-2006Q1:1.21.0.2 pkgsrc-2006Q1-base:1.21 pkgsrc-2005Q4:1.19.0.2 pkgsrc-2005Q4-base:1.19 pkgsrc-2005Q3:1.17.0.4 pkgsrc-2005Q3-base:1.17 pkgsrc-2005Q2:1.17.0.2 pkgsrc-2005Q2-base:1.17 pkgsrc-2005Q1:1.16.0.4 pkgsrc-2005Q1-base:1.16 pkgsrc-2004Q4:1.16.0.2 pkgsrc-2004Q4-base:1.16 pkgsrc-2004Q3:1.15.0.4 pkgsrc-2004Q3-base:1.15 pkgsrc-2004Q2:1.15.0.2 pkgsrc-2004Q2-base:1.15 pkgsrc-2004Q1:1.14.0.2 pkgsrc-2004Q1-base:1.14 pkgsrc-2003Q4:1.13.0.2 pkgsrc-2003Q4-base:1.13 netbsd-1-6-1:1.6.0.2 netbsd-1-6-1-base:1.6 pkgsrc-base:1.1.1.1 TNF:1.1.1; locks; strict; comment @# @; 1.66 date 2023.07.17.14.15.43; author ryoon; state Exp; branches; next 1.65; commitid ZDOLZdu7aMAnaaxE; 1.65 date 2023.04.14.03.37.52; author ryoon; state Exp; branches; next 1.64; commitid AxyYAf2M1jsTE1lE; 1.64 date 2022.09.05.13.24.27; author ryoon; state Exp; branches; next 1.63; commitid AIqqVJOHZX9y0GSD; 1.63 date 2022.06.28.11.36.10; author wiz; state Exp; branches; next 1.62; commitid D2UoJrTHpoHEANJD; 1.62 date 2021.08.15.17.08.24; author wiz; state Exp; branches; next 1.61; commitid 74cjBapBG2AAE55D; 1.61 date 2021.05.24.19.54.24; author wiz; state Exp; branches; next 1.60; commitid qokaiStTApGMcrUC; 1.60 date 2020.09.30.19.22.08; author ryoon; state Exp; branches; next 1.59; commitid XbzeHM1ZwTggE6qC; 1.59 date 2020.08.31.18.11.42; author wiz; state Exp; branches; next 1.58; commitid 7zxRbfOkDOoxbfmC; 1.58 date 2020.05.03.08.00.42; author rillig; state Exp; branches; next 1.57; commitid TnzJoSaa7grmHL6C; 1.57 date 2019.12.15.22.09.30; author wiz; state Exp; branches; next 1.56; commitid R4BqogAWhsbCTQOB; 1.56 date 2019.12.15.21.12.33; author rhialto; state Exp; branches; next 1.55; commitid Ik6RylltbHNrzQOB; 1.55 date 2019.08.11.13.23.23; author wiz; state Exp; branches; next 1.54; commitid Ifet9Pg6Qt99ZByB; 1.54 date 2019.06.11.10.17.28; author jperkin; state Exp; branches; next 1.53; commitid y3cNXlGFwuJKXKqB; 1.53 date 2018.08.22.09.46.45; author wiz; state Exp; branches; next 1.52; commitid YLub8g3ofvFGb6PA; 1.52 date 2018.02.27.15.16.50; author rillig; state Exp; branches; next 1.51; commitid az4vwYMjhqO2HvsA; 1.51 date 2017.08.18.21.51.40; author adam; state Exp; branches; next 1.50; commitid eGvvDuPGsBxm5K3A; 1.50 date 2017.03.30.19.23.17; author ryoon; state Exp; branches; next 1.49; commitid gbngwzARRvlyNBLz; 1.49 date 2017.03.30.08.52.54; author bouyer; state Exp; branches; next 1.48; commitid YUOojVzss4vGiyLz; 1.48 date 2017.01.30.04.46.13; author wen; state Exp; branches 1.48.2.1; next 1.47; commitid zIO681R3ur07QWDz; 1.47 date 2016.07.09.06.39.05; author wiz; state Exp; branches; next 1.46; commitid dlqnocGpOoXV2Cdz; 1.46 date 2016.03.14.13.16.31; author ryoon; state Exp; branches; next 1.45; commitid Rbz9Y9BxFIh11CYy; 1.45 date 2016.02.12.23.28.43; author ryoon; state Exp; branches; next 1.44; commitid 1B1QD0mG0rwQoGUy; 1.44 date 2015.11.20.19.04.49; author ryoon; state Exp; branches; next 1.43; commitid H26q6gAMXTcIDRJy; 1.43 date 2015.06.12.10.51.20; author wiz; state Exp; branches; next 1.42; commitid B4JmCfaVUbiY38py; 1.42 date 2014.11.25.20.19.03; author ryoon; state Exp; branches; next 1.41; commitid cr4YB0lhppPACBZx; 1.41 date 2014.07.15.14.28.07; author ryoon; state Exp; branches; next 1.40; commitid kSltMOltxd4iXtIx; 1.40 date 2014.05.29.23.37.34; author wiz; state Exp; branches; next 1.39; commitid laryHfkCalgYtuCx; 1.39 date 2014.05.27.06.31.28; author adam; state Exp; branches; next 1.38; commitid xnatxLlBRKpkT8Cx; 1.38 date 2014.02.23.15.30.31; author adam; state Exp; branches; next 1.37; commitid HXEAFwnZTuLrReqx; 1.37 date 2014.01.11.10.52.09; author adam; state Exp; branches; next 1.36; commitid vholjAcB2GsPHGkx; 1.36 date 2013.10.27.23.22.54; author wiz; state Exp; branches; next 1.35; commitid izaGCFUQZJqRiZax; 1.35 date 2013.05.31.12.42.07; author wiz; state Exp; branches; next 1.34; commitid hIeXGcx6VfKHwMRw; 1.34 date 2012.12.31.00.27.37; author sbd; state Exp; branches; next 1.33; 1.33 date 2012.12.18.12.08.25; author tron; state Exp; branches; next 1.32; 1.32 date 2012.12.06.11.43.24; author jperkin; state Exp; branches; next 1.31; 1.31 date 2012.10.25.06.55.51; author asau; state Exp; branches; next 1.30; 1.30 date 2012.10.03.21.57.48; author wiz; state Exp; branches; next 1.29; 1.29 date 2012.08.21.18.04.58; author adam; state Exp; branches; next 1.28; 1.28 date 2012.08.03.13.07.54; author adam; state Exp; branches; next 1.27; 1.27 date 2012.06.01.19.47.46; author cheusov; state Exp; branches; next 1.26; 1.26 date 2012.05.29.22.10.24; author cheusov; state Exp; branches; next 1.25; 1.25 date 2011.04.22.13.44.49; author obache; state Exp; branches; next 1.24; 1.24 date 2008.03.08.12.16.43; author tnn; state Exp; branches; next 1.23; 1.23 date 2006.04.13.18.23.38; author jlam; state Exp; branches; next 1.22; 1.22 date 2006.04.07.19.54.17; author jlam; state Exp; branches; next 1.21; 1.21 date 2006.03.05.16.27.28; author jlam; state Exp; branches; next 1.20; 1.20 date 2006.02.05.23.11.02; author joerg; state Exp; branches; next 1.19; 1.19 date 2005.12.05.23.55.20; author rillig; state Exp; branches; next 1.18; 1.18 date 2005.12.05.20.51.03; author rillig; state Exp; branches; next 1.17; 1.17 date 2005.04.11.21.47.34; author tv; state Exp; branches; next 1.16; 1.16 date 2004.10.03.00.18.19; author tv; state Exp; branches; next 1.15; 1.15 date 2004.04.25.05.03.43; author snj; state Exp; branches; next 1.14; 1.14 date 2004.02.09.08.13.04; author grant; state Exp; branches; next 1.13; 1.13 date 2003.09.18.19.13.50; author wiz; state Exp; branches; next 1.12; 1.12 date 2003.08.09.11.27.48; author seb; state Exp; branches; next 1.11; 1.11 date 2003.08.02.05.19.57; author grant; state Exp; branches; next 1.10; 1.10 date 2003.07.30.17.00.04; author grant; state Exp; branches; next 1.9; 1.9 date 2003.07.17.22.54.16; author grant; state Exp; branches; next 1.8; 1.8 date 2003.07.13.13.53.32; author wiz; state Exp; branches; next 1.7; 1.7 date 2003.06.24.05.29.06; author grant; state Exp; branches; next 1.6; 1.6 date 2003.02.13.07.33.34; author wiz; state Exp; branches; next 1.5; 1.5 date 2003.01.09.17.23.10; author cjep; state Exp; branches; next 1.4; 1.4 date 2002.12.25.19.54.58; author wiz; state Exp; branches; next 1.3; 1.3 date 2002.12.25.19.50.34; author wiz; state Exp; branches; next 1.2; 1.2 date 2002.12.06.15.29.20; author cjep; state Exp; branches; next 1.1; 1.1 date 2002.10.14.16.43.14; author bouyer; state Exp; branches 1.1.1.1; next ; 1.48.2.1 date 2017.04.01.14.55.18; author bsiegert; state Exp; branches; next ; commitid RNAFnjYqu3wFfQLz; 1.1.1.1 date 2002.10.14.16.43.14; author bouyer; state Exp; branches; next ; desc @@ 1.66 log @grep: Update to 3.11 Changelog: * Noteworthy changes in release 3.11 (2023-05-13) [stable] ** 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. @ text @# $NetBSD: Makefile,v 1.65 2023/04/14 03:37:52 ryoon Exp $ DISTNAME= grep-3.11 CATEGORIES= textproc MASTER_SITES= ${MASTER_SITE_GNU:=grep/} EXTRACT_SUFX= .tar.xz MAINTAINER= pkgsrc-users@@pkgsrc.org HOMEPAGE= https://www.gnu.org/software/grep/grep.html COMMENT= GNU grep LICENSE= gnu-gpl-v3 # or later USE_PKGLOCALEDIR= yes USE_TOOLS+= bash makeinfo msgfmt GNU_CONFIGURE= yes CONFIGURE_ARGS+= --enable-perl-regexp CONFIGURE_ARGS+= --program-prefix=g CONFIGURE_ENV+= MKDIR_P=${INSTALL_DATA_DIR:Q} CONFIGURE_ENV+= PERL= # none INFO_FILES= yes TEXINFO_REQD= 4.0 INSTALLATION_DIRS= ${PKGGNUDIR}bin ${PKGGNUDIR}${PKGMANDIR}/man1 .include "../../mk/bsd.prefs.mk" .if ${OS_VARIANT} == "SCOOSR5" # SCO OpenServer 5.0.7/3.2's pthread is builtin GNU pth. CONFIGURE_ARGS+= --enable-threads=pth .endif post-install: .for g n in bin/ggrep ${PKGGNUDIR}bin/grep bin/gegrep ${PKGGNUDIR}bin/egrep \ bin/gfgrep ${PKGGNUDIR}bin/fgrep \ man/man1/ggrep.1 ${PKGGNUDIR}${PKGMANDIR}/man1/grep.1 \ man/man1/ggrep.1 ${PKGGNUDIR}${PKGMANDIR}/man1/egrep.1 \ man/man1/ggrep.1 ${PKGGNUDIR}${PKGMANDIR}/man1/fgrep.1 ${LN} -sf ${PREFIX}/${g} ${DESTDIR}${PREFIX}/${n} .endfor .include "../../devel/gettext-lib/buildlink3.mk" .include "../../devel/pcre2/buildlink3.mk" .include "../../mk/bsd.pkg.mk" @ 1.65 log @grep: Update to 3.10 Changelog: * Noteworthy changes in release 3.10 (2023-03-22) [stable] ** Bug fixes With -P, \d now matches only ASCII digits, regardless of PCRE options/modes. The changes in grep-3.9 to make \b and \w work properly had the undesirable side effect of making \d also match e.g., the Arabic digits: ٠١٢٣٤٥٦٧٨٩. With grep-3.9, -P '\d+' would match that ten-digit (20-byte) string. Now, to match such a digit, you would use \p{Nd}. Similarly, \D is now mapped to [^0-9]. [bug introduced in grep 3.9] * Noteworthy changes in release 3.9 (2023-03-05) [stable] ** Bug fixes With -P, some non-ASCII UTF8 characters were not recognized as word-constituent due to our omission of the PCRE2_UCP flag. E.g., given f(){ echo Perú|LC_ALL=en_US.UTF-8 grep -Po "$1"; } and this command, echo $(f 'r\w'):$(f '.\b'), before it would print ":r". After the fix, it prints the correct results: "rú:ú". When given multiple patterns the last of which has a back-reference, grep no longer sometimes mistakenly matches lines in some cases. [Bug#36148#13 introduced in grep 3.4] @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.64 2022/09/05 13:24:27 ryoon Exp $ d3 1 a3 1 DISTNAME= grep-3.10 @ 1.64 log @grep: Update to 3.8 Changelog: * Noteworthy changes in release 3.8 (2022-09-02) [stable] ** Changes in behavior The -P option is now based on PCRE2 instead of the older PCRE, thanks to code contributed by Carlo Arenas. The egrep and fgrep commands, which have been deprecated since release 2.5.3 (2007), now warn that they are obsolescent and should be replaced by grep -E and grep -F. The confusing GREP_COLOR environment variable is now obsolescent. Instead of GREP_COLOR='xxx', use GREP_COLORS='mt=xxx'. grep now warns if GREP_COLOR is used and is not overridden by GREP_COLORS. Also, grep now treats GREP_COLOR like GREP_COLORS by silently ignoring it if it attempts to inject ANSI terminal escapes. Regular expressions with stray backslashes now cause warnings, as their unspecified behavior can lead to unexpected results. For example, '\a' and 'a' are not always equivalent . Similarly, regular expressions or subexpressions that start with a repetition operator now also cause warnings due to their unspecified behavior; for example, *a(+b|{1}c) now has three reasons to warn. The warnings are intended as a transition aid; they are likely to be errors in future releases. Regular expressions like [:space:] are now errors even if POSIXLY_CORRECT is set, since POSIX now allows the GNU behavior. ** Bug fixes In locales using UTF-8 encoding, the regular expression '.' no longer sometimes fails to match Unicode characters U+D400 through U+D7FF (some Hangul Syllables, and Hangul Jamo Extended-B) and Unicode characters U+108000 through U+10FFFF (half of Supplemental Private Use Area plane B). [bug introduced in grep 3.4] The -s option no longer suppresses "binary file matches" messages. [Bug#51860 introduced in grep 3.5] ** Documentation improvements The manual now covers unspecified behavior in patterns like \x, (+), and range expressions outside the POSIX locale. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.63 2022/06/28 11:36:10 wiz Exp $ d3 1 a3 1 DISTNAME= grep-3.8 @ 1.63 log @*: recursive bump for perl 5.36 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.62 2021/08/15 17:08:24 wiz Exp $ d3 1 a3 2 DISTNAME= grep-3.7 PKGREVISION= 1 d42 1 a42 1 .include "../../devel/pcre/buildlink3.mk" @ 1.62 log @grep: update to 3.7. ** Changes in behavior Use of the --unix-byte-offsets (-u) option now evokes a warning. Since 3.1, this Windows-only option has had no effect. ** Bug fixes Preprocessing N patterns would take at least O(N^2) time when too many patterns hashed to too few buckets. This now takes seconds, not days: : | grep -Ff <(seq 6400000 | tr 0-9 A-J) [Bug#44754 introduced in grep 3.5] * Noteworthy changes in release 3.6 (2020-11-08) [stable] ** Changes in behavior The GREP_OPTIONS environment variable no longer affects grep's behavior. The variable was declared obsolescent in grep 2.21 (2014), and since then any use had caused grep to issue a diagnostic. ** Bug fixes grep's DFA matcher performed an invalid regex transformation that would convert an ERE like a+a+a+ to a+a+, which would make grep a+a+a+ mistakenly match "aa". [Bug#44351 introduced in grep 3.2] grep -P now reports the troublesome input filename upon PCRE execution failure. Before, searching many files for something rare might fail with just "exceeded PCRE's backtracking limit". Now, it also reports which file triggered the failure. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.61 2021/05/24 19:54:24 wiz Exp $ d4 1 @ 1.61 log @*: recursive bump for perl 5.34 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.60 2020/09/30 19:22:08 ryoon Exp $ d3 1 a3 2 DISTNAME= grep-3.5 PKGREVISION= 1 @ 1.60 log @grep: Update to 3.5 Changelog: * Noteworthy changes in release 3.5 (2020-09-27) [stable] ** Changes in behavior The message that a binary file matches is now sent to standard error and the message has been reworded from "Binary file FOO matches" to "grep: FOO: binary file matches", to avoid confusion with ordinary output or when file names contain spaces and the like, and to be more consistent with other diagnostics. For example, commands like 'grep PATTERN FILE | wc' no longer add 1 to the count of matching text lines due to the presence of the message. Like other stderr messages, the message is now omitted if the --no-messages (-s) option is given. Two other stderr messages now use the typical form too. They are now "grep: FOO: warning: recursive directory loop" and "grep: FOO: input file is also the output". The --files-without-match (-L) option has reverted to its behavior in grep 3.1 and earlier. That is, grep -L again succeeds when a line is selected, not when a file is listed. The behavior in grep 3.2 through 3.4 was causing compatibility problems. ** Bug fixes grep -I no longer issues a spurious "Binary file FOO matches" line. [Bug#33552 introduced in grep 2.23] In UTF-8 locales, grep -w no longer ignores a multibyte word constituent just before what would otherwise be a word match. [Bug#43225 introduced in grep 2.28] grep -i no longer mishandles ASCII characters that match multibyte characters. For example, 'LC_ALL=tr_TR.utf8 grep -i i' no longer dumps core merely because 'i' matches 'İ' (U+0130 LATIN CAPITAL LETTER I WITH DOT ABOVE) in Turkish when ignoring case. [Bug#43577 introduced partly in grep 2.28 and partly in grep 3.4] A performance regression with -E and many patterns has been mostly fixed. "Mostly" as there is a performance tradeoff between Bug#22357 and Bug#40634. [Bug#40634 introduced in grep 2.28] A performance regression with many duplicate patterns has been fixed. [Bug#43040 introduced in grep 3.4] An N^2 RSS performance regression with many patterns has been fixed in common cases (no backref, and no use of -o or --color). With only 80,000 lines of /usr/share/dict/linux.words, the following would use 100GB of RSS and take 3 minutes. With the fix, it used less than 400MB and took less than one second: head -80000 /usr/share/dict/linux.words > w; grep -vf w w [Bug#43527 introduced in grep 3.4] ** Build-related "make dist" builds .tar.gz files again, as they are still used in some barebones builds. * Noteworthy changes in release 3.4 (2020-01-02) [stable] ** New features The new --no-ignore-case option causes grep to observe case distinctions, overriding any previous -i (--ignore-case) option. ** Bug fixes '.' no longer matches some invalid byte sequences in UTF-8 locales. [bug introduced in grep 2.7] grep -Fw can no longer false match in non-UTF-8 multibyte locales For example, this command would erroneously print its input line: echo ab | LC_CTYPE=ja_JP.eucjp grep -Fw b [Bug#38223 introduced in grep 2.28] The exit status of 'grep -L' is no longer incorrect when standard output is /dev/null. [Bug#37716 introduced in grep 3.2] A performance bug has been fixed when grep is given many patterns, each with no back-reference. [Bug#33249 introduced in grep 2.5] A performance bug has been fixed for patterns like '01.2' that cause grep to reorder tokens internally. [Bug#34951 introduced in grep 3.2] ** Build-related The build procedure no longer relies on any already-built src/grep that might be absent or broken. Instead, it uses the system 'grep' to bootstrap, and uses src/grep only to test the build. On Solaris /usr/bin/grep is broken, but you can install GNU or XPG4 'grep' from the standard Solaris distribution before building GNU Grep yourself. [bug introduced in grep 2.8] @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.59 2020/08/31 18:11:42 wiz Exp $ d4 1 @ 1.59 log @*: bump PKGREVISION for perl-5.32. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.58 2020/05/03 08:00:42 rillig Exp $ d3 1 a3 2 DISTNAME= grep-3.3 PKGREVISION= 1 d14 1 a14 1 USE_TOOLS+= makeinfo msgfmt @ 1.58 log @textproc/grep: suppress USE_TOOLS+=perl warning @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.57 2019/12/15 22:09:30 wiz Exp $ d4 1 @ 1.57 log @grep: reset PKGREVISION after update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.56 2019/12/15 21:12:33 rhialto Exp $ d19 1 @ 1.56 log @textproc/grep: update to 3.3 * Noteworthy changes in release 3.3 (2018-12-20) [stable] ** Bug fixes Some uses of \b in the C locale and with the DFA matcher would fail, e.g., the following would print nothing (it should print the input line): echo 123-x|LC_ALL=C grep '.\bx' Using a multibyte locale, using certain regexp constructs (some ranges, backreferences), or forcing use of the PCRE matcher via --perl-regexp (-P) would avoid the bug. [bug introduced in grep 2.3] * Noteworthy changes in release 3.2 (2018-12-20) [stable] ** Changes in behavior The --files-without-match (-L) option now causes grep to succeed when a file is listed, instead of when a line is selected. This resembles what git-grep does. ** Bug fixes The --recursive (-r) option no longer fails on MS-Windows. [bug introduced in grep 2.11] ** Improvements An over-30x performance improvement when many 'or'd expressions share a common prefix, thanks to improvements in gnulib's dfa.c, by Norihiro Tanaka. See gnulib commits v0.1-2110-ge648401be, v0.1-2111-g4299106ce, v0.1-2117-g617a60974 An additional 3-23% speed-up when searching large files, via increased initial buffer size. grep now diagnoses stack overflow. Before grep-2.6, the included regexp code would detect it. Since 2.6, grep defaulted to using glibc's regexp, which lost that capability. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.55 2019/08/11 13:23:23 wiz Exp $ a3 1 PKGREVISION= 4 @ 1.55 log @Bump PKGREVISIONs for perl 5.30.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.54 2019/06/11 10:17:28 jperkin Exp $ d3 1 a3 1 DISTNAME= grep-3.1 @ 1.54 log @grep: Ensure we use the correct path to PKGGNUDIR grep. Remove pointless patch-src_Makefile.am. Bump PKGREVISION. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.53 2018/08/22 09:46:45 wiz Exp $ d4 1 a4 1 PKGREVISION= 3 @ 1.53 log @Recursive bump for perl5-5.28.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.52 2018/02/27 15:16:50 rillig Exp $ d4 1 a5 1 PKGREVISION= 2 @ 1.52 log @textproc/grep: enable PCRE for GNU Grep It had been disabled in 2003 for no apparent reason. ok @@bouyer @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.51 2017/08/18 21:51:40 adam Exp $ d5 1 a5 1 PKGREVISION= 1 @ 1.51 log @release 3.1: ** Improvements grep '[0-9]' is now just as fast as grep '[[:digit:]]' when run in a multi-byte locale. Before, it was several times slower. ** Changes in behavior Context no longer excludes selected lines omitted because of -m. For example, 'grep "^" -m1 -A1' now outputs the first two input lines, not just the first line. This fixes a glitch that has been present since -m was added in grep 2.5. The following changes affect only MS-Windows platforms. First, the --binary (-U) option now governs whether binary I/O is used, instead of a heuristic that was sometimes incorrect. Second, the --unix-byte-offsets (-u) option now has no effect on MS-Windows too. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.50 2017/03/30 19:23:17 ryoon Exp $ d5 1 d9 2 a10 2 MAINTAINER= bouyer@@NetBSD.org HOMEPAGE= http://www.gnu.org/software/grep/grep.html d17 1 a17 1 CONFIGURE_ARGS+= --disable-perl-regexp d42 1 @ 1.50 log @Update to 3.0 Changelog: * Noteworthy changes in release 3.0 (2017-02-09) [stable] ** Bug fixes grep without -F no longer goes awry when given two or more patterns that contain no special characters other than '\' and also contain a subpattern like '\.' that escapes a character to make it ordinary. [bug introduced in grep 2.28] grep no longer fails to build on PCRE versions before 8.20. [bug introduced in grep 2.28] * Noteworthy changes in release 2.28 (2017-02-06) [stable] ** Bug fixes When grep -Fo finds matches of differing length, it could mistakenly print a shorter one. Now it prints a longest one. [bug introduced in grep-2.26] When standard output is /dev/null, grep no longer fails when standard input is a file in the Linux /proc file system, or when standard input is a pipe and standard output is in append mode. [bugs introduced in grep-2.27] Fix performance regression with multiple patterns, e.g., for -Fi in a multi-byte locale, or for -Fw in a single-byte locale. [bugs introduced in grep-2.19, grep-2.22 and grep-2.26] ** Improvements Improve performance for -E or -G pattern lists that are easily converted to -F format. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.49 2017/03/30 08:52:54 bouyer Exp $ d3 1 a3 1 DISTNAME= grep-3.0 @ 1.49 log @Use absolute paths in /usr/pkg/bin/g*grep, so they can be used even if /usr/pkg/bin/ is not in $PATH. Bump PKGREVISION From Tim Zingelman @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.48 2017/01/30 04:46:13 wen Exp $ d3 1 a3 1 DISTNAME= grep-2.27 a6 1 PKGREVISION= 1 @ 1.48 log @Update to 2.27 Upstream changes: * Noteworthy changes in release 2.27 (2016-12-06) [stable] ** Bug fixes grep no longer reports a false match in a multibyte, non-UTF8 locale like zh_CN.gb18030, with a regular expression like ".*7" that just happens to match the 4-byte representation of gb18030's \uC9, the final byte of which is the digit "7". [bug introduced in grep-2.19] grep by default now reads all of standard input if it is a pipe, even if this cannot affect grep's output or exit status. This works better with nonportable scripts that run "PROGRAM | grep PATTERN >/dev/null" where PROGRAM dies when writing into a broken pipe. [bug introduced in grep-2.26] grep no longer mishandles ranges in nontrivial unibyte locales. [bug introduced in grep-2.26] grep -P no longer attempts multiline matches. This works more intuitively with unusual patterns, and means that grep -Pz no longer rejects patterns containing ^ and $ and works when combined with -x. [bugs introduced in grep-2.23] A downside is that grep -P is now significantly slower, albeit typically still faster than pcregrep. grep -m0 -L PAT FILE now outputs "FILE". [bug introduced in grep-2.5] To output ':' and tab-align the following character C, grep -T no longer outputs tab-backspace-':'-C, an approach that has problems if run inside an Emacs shell window. [bug introduced in grep-2.5.2] grep -T now uses worst-case widths of line numbers and byte offsets instead of guessing widths that might not work with larger files. [bug introduced in grep-2.5.2] grep's use of getprogname no longer causes a build failure on HP-UX. ** Improvements grep no longer reads the input in a few more cases when it is easy to see that matching cannot succeed, e.g., 'grep -f /dev/null'. * Noteworthy changes in release 2.26 (2016-10-02) [stable] ** Bug fixes Grep no longer omits output merely because it follows an output line suppressed due to encoding errors. [bug introduced in grep-2.21] In the Shift_JIS locale, grep no longer mistakenly matches in the middle of a multibyte character. [bug present since "the beginning"] ** Improvements grep can be much faster now when standard output is /dev/null. grep -F is now typically much faster when many patterns are given, as it now uses the Aho-Corasick algorithm instead of the Commentz-Walter algorithm in that case. grep -iF is typically much faster in a multibyte locale, if the pattern and its case counterparts contain only single byte characters. grep with complicated expressions (e.g., back-references) and without -i now uses the regex fastmap for better performance. In multibyte locales, grep now handles leading "." in patterns more efficiently. grep now prints a "FILENAME:LINENO: " prefix when diagnosing an invalid regular expression that was read from an '-f'-specified file. * Noteworthy changes in release 2.25 (2016-04-21) [stable] ** Bug fixes In the C or POSIX locale, grep now treats all bytes as valid characters even if the C runtime library says otherwise. The revised behavior is more compatible with the original intent of POSIX, and the next release of POSIX will likely make this official. [bug introduced in grep-2.23] grep -Pz no longer mistakenly diagnoses patterns like [^a] that use negated character classes. [bug introduced in grep-2.24] grep -oz now uses null bytes, not newlines, to terminate output lines. [bug introduced in grep-2.5] ** Improvements grep now outputs details more consistently when reporting a write error. E.g., "grep: write error: No space left on device" rather than just "grep: write error". @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.47 2016/07/09 06:39:05 wiz Exp $ d7 1 @ 1.48.2.1 log @Pullup ticket #5225 - requested by sevan textproc/grep: bugfix Revisions pulled up: - textproc/grep/Makefile 1.49 - textproc/grep/distinfo 1.22 - textproc/grep/patches/patch-src_Makefile.am 1.1 - textproc/grep/patches/patch-src_Makefile.in 1.1 --- Module Name: pkgsrc Committed By: bouyer Date: Thu Mar 30 08:52:54 UTC 2017 Modified Files: pkgsrc/textproc/grep: Makefile distinfo Added Files: pkgsrc/textproc/grep/patches: patch-src_Makefile.am patch-src_Makefile.in Log Message: Use absolute paths in /usr/pkg/bin/g*grep, so they can be used even if /usr/pkg/bin/ is not in $PATH. Bump PKGREVISION >From Tim Zingelman @ text @d1 1 a1 1 # $NetBSD$ a6 1 PKGREVISION= 1 @ 1.47 log @Bump PKGREVISION for perl-5.24.0 for everything mentioning perl. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.46 2016/03/14 13:16:31 ryoon Exp $ d3 1 a3 2 DISTNAME= grep-2.24 PKGREVISION= 1 @ 1.46 log @Update to 2.24 Changelog: * Noteworthy changes in release 2.24 (2016-03-10) [stable] ** Bug fixes grep -z would match strings it should not. To trigger the bug, you'd have to use a regular expression including an anchor (^ or $) and a feature like a range or a backreference, causing grep to forego its DFA matcher and resort to using re_search. With a multibyte locale, that matcher could mistakenly match a string containing a newline. For example, this command: printf 'a\nb\0' | LC_ALL=en_US.utf-8 grep -z '^[a-b]*b' would mistakenly match and print all four input bytes. After the fix, there is no match, as expected. [bug introduced in grep-2.7] grep -Pz now diagnoses attempts to use patterns containing ^ and $, instead of mishandling these patterns. This problem seems to be inherent to the PCRE API; removing this limitation is on PCRE's maint/README wish list. Patterns can continue to match literal ^ and $ by escaping them with \ (now needed even inside [...]). [bug introduced in grep-2.5] @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.45 2016/02/12 23:28:43 ryoon Exp $ d4 1 @ 1.45 log @Update to 2.23 Changelog: * Noteworthy changes in release 2.23 (2016-02-04) [stable] ** Bug fixes Binary files are now less likely to generate diagnostics and more likely to yield text matches. grep now reports "Binary file FOO matches" and suppresses further output instead of outputting a line containing an encoding error; hence grep can now report matching text before a later binary match. Formerly, grep reported FOO to be binary when it found an encoding error in FOO before generating output for FOO, which meant it never reported both matching text and matching binary data; this was less useful for searching text containing encoding errors in non-matching lines. [bug introduced in grep-2.21] grep -c no longer stops counting when finding binary data. [bug introduced in grep-2.21] grep no longer outputs encoding errors in unibyte locales. For example, if the byte '\x81' is not a valid character in a unibyte locale, grep treats the byte as binary data. [bug introduced in grep-2.21] grep -oP is no longer susceptible to an infinite loop when processing invalid UTF8 just before a match. [bug introduced in grep-2.22] --exclude and related options are now matched against trailing parts of command-line arguments, not against the entire arguments. This partly reverts the --exclude-related change in 2.22. [bug introduced in grep-2.22] --line-buffer is no longer ineffective when combined with -l. [bug introduced in grep-2.5] -xw is now equivalent to -x more consistently, with -P and with backrefs. [bug only partially fixed in grep-2.19] @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.44 2015/11/20 19:04:49 ryoon Exp $ d3 1 a3 1 DISTNAME= grep-2.23 @ 1.44 log @Update to 2.22 Changelog: * Noteworthy changes in release 2.22 (2015-11-01) [stable] ** Improvements Performance has improved for patterns containing very long strings, reducing preprocessing time for an N-byte regexp from O(N^2) to only slightly superlinear for most patterns. Before, a command like the following would take over a minute, but now, it takes less than a second: : | grep -f <(seq -s '' 99999) When building grep, 'configure' now uses PCRE's pkg-config module for configuration information, rather than attempting to guess it by hand. ** Bug fixes A DFA matcher bug made this command mistakenly print its input line: echo axb | grep -E '^x|x$' Likewise for this equivalent command: echo axb | grep -e '^x' -e 'x$' [bug introduced in grep-2.19 ] grep no longer reads from uninitialized memory or from beyond the end of the heap-allocated input buffer. This fix addressed CVE-2015-1345. [bug introduced in grep-2.19 ] With -z, '.' and '[^x]' in a pattern now consistently match newline. Previously, they sometimes matched newline, and sometimes did not. [bug introduced in grep-2.4] When the JIT stack is exhausted, grep -P now grows the stack rather than reporting an internal PCRE error. 'grep -D skip PATTERN FILE' no longer hangs if FILE is a fifo. [bug introduced in grep-2.12] --exclude and related options are now matched against entire command-line arguments, not against command-line components. [bug introduced in grep-2.6] Fix performance degradation of grep -Fw in unibyte locales. [bug introduced in grep-2.19 ] @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.43 2015/06/12 10:51:20 wiz Exp $ d3 1 a3 1 DISTNAME= grep-2.22 @ 1.43 log @Recursive PKGREVISION bump for all packages mentioning 'perl', having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.42 2014/11/25 20:19:03 ryoon Exp $ d3 1 a3 2 DISTNAME= grep-2.21 PKGREVISION= 1 @ 1.42 log @Update to 2.21 Changelog: * Noteworthy changes in release 2.21 (2014-11-23) [stable] ** Improvements Performance has been greatly improved for searching files containing holes, on platforms where lseek's SEEK_DATA flag works efficiently. Performance has improved for rejecting data that cannot match even the first part of a nontrivial pattern. Performance has improved for very long strings in patterns. If a file contains data improperly encoded for the current locale, and this is discovered before any of the file's contents are output, grep now treats the file as binary. grep -P no longer reports an error and exits when given invalid UTF-8 data. Instead, it considers the data to be non-matching. ** Bug fixes grep no longer mishandles patterns that contain \w or \W in multibyte locales. grep would fail to count newlines internally when operating in non-UTF8 multibyte locales, leading it to print potentially many lines that did not match. E.g., the command, "seq 10 | env LC_ALL=zh_CN src/grep -n .." would print this: 1:1 2 3 4 5 6 7 8 9 10 implying that the match, "10" was on line 1. [bug introduced in grep-2.19] grep -F -x -o no longer prints an extra newline for each match. [bug introduced in grep-2.19] grep in a non-UTF8 multibyte locale could mistakenly match in the middle of a multibyte character when using a '^'-anchored alternate in a pattern, leading it to print non-matching lines. [bug present since "the beginning"] grep -F Y no longer fails to match in non-UTF8 multibyte locales like Shift-JIS, when the input contains a 2-byte character, XY, followed by the single-byte search pattern, Y. grep would find the first, middle- of-multibyte matching "Y", and then mistakenly advance an internal pointer one byte too far, skipping over the target "Y" just after that. [bug introduced in grep-2.19] grep -E rejected unmatched ')', instead of treating it like '\)'. [bug present since "the beginning"] On NetBSD, grep -r no longer reports "Inappropriate file type or format" when refusing to follow a symbolic link. [bug introduced in grep-2.12] ** Changes in behavior The GREP_OPTIONS environment variable is now obsolescent, and grep now warns if it is used. Please use an alias or script instead. In locales with multibyte character encodings other than UTF-8, grep -P now reports an error and exits instead of misbehaving. When searching binary data, grep now may treat non-text bytes as line terminators. This can boost performance significantly. grep -z no longer automatically treats the byte '\200' as binary data. * Noteworthy changes in release 2.20 (2014-06-03) [stable] ** Bug fixes grep --max-count=N FILE would no longer stop reading after the Nth match. I.e., while grep would still print the correct output, it would continue reading until end of input, and hence, potentially forever. [bug introduced in grep-2.19] A command like echo aa|grep -E 'a(b$|c$)' would mistakenly report the input as a matched line. [bug introduced in grep-2.19] ** Changes in behavior grep --exclude-dir='FOO/' now excludes the directory FOO. Previously, the trailing slash meant the option was ineffective. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.41 2014/07/15 14:28:07 ryoon Exp $ d4 1 @ 1.41 log @Fix broken binary under SCO OpenServer 5.0.7/3.2. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.40 2014/05/29 23:37:34 wiz Exp $ d3 1 a3 2 DISTNAME= grep-2.19 PKGREVISION= 2 @ 1.40 log @Bump for perl-5.20.0. Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.39 2014/05/27 06:31:28 adam Exp $ d4 1 a4 1 PKGREVISION= 1 d27 5 @ 1.39 log @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). @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.38 2014/02/23 15:30:31 adam Exp $ d4 1 @ 1.38 log @Changes 2.18: Bug fixes: * grep no longer mishandles patterns like [^^-~] in unibyte locales. * grep -i in a multibyte, non-UTF8 locale could be up to 200 times slower than in 2.16. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.37 2014/01/11 10:52:09 adam Exp $ d3 1 a3 1 DISTNAME= grep-2.18 @ 1.37 log @Changes 2.16: ** Bug fixes Fix gnulib-provided maint.mk so that the release procedure described in README-release actually does what we want. Before that fix, that procedure resulted in a grep-2.15 tarball that would lead to a grep binary whose --version-reported version number was 2.14.51... The fix to make \s and \S work with multi-byte white space broke the use of each shortcut whenever followed by a repetition operator. For example, \s*, \s+, \s? and \s{3} would all malfunction in a multi-byte locale. [bug introduced in grep-2.15] The fix to make grep -P work better with UTF-8 made it possible for grep to evoke a larger set of PCRE errors, some of which could trigger an abort. E.g., this would abort: printf '\x82'|LC_ALL=en_US.UTF-8 grep -P y Now grep handles arbitrary PCRE errors. [bug introduced in grep-2.15] Handle very long lines (2GiB and longer) on systems with a deficient read system call. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.36 2013/10/27 23:22:54 wiz Exp $ d3 1 a3 1 DISTNAME= grep-2.16 @ 1.36 log @Update to 2.15: * Noteworthy changes in release 2.15 (2013-10-26) [stable] ** Bug fixes grep's \s and \S failed to work with multi-byte white space characters. For example, \s would fail to match a non-breaking space, and this would print nothing: printf '\xc2\xa0' | LC_ALL=en_US.UTF-8 grep '\s' A related bug is that \S would mistakenly match an invalid multibyte character. For example, the following would match: printf '\x82\n' | LC_ALL=en_US.UTF-8 grep '^\S$' [bug present since grep-2.6] grep -i would segfault on systems using UTF-16-based wchar_t (Cygwin) when converting an input string containing certain 4-byte UTF-8 sequences to lower case. The conversions to wchar_t and back to a UTF-8 multibyte string did not take surrogate pairs into account. [bug present since at least grep-2.6, though the segfault is new with 2.13] grep -E would segfault when given a regexp like '([^.]*[M]){1,2}' for any multibyte character M. [bug introduced in grep-2.6, which would segfault, but 2.7 and 2.8 had no problem, and 2.9 through 2.14 would hit a failed assertion. ] grep -F would get stuck in an infinite loop when given a search string that is an invalid byte sequence in the current locale and that matches the bytes of the input twice on a line. Now grep fails with exit status 1. grep -P could misbehave. While multi-byte mode is only supported by PCRE with UTF-8 locales, grep did not activate it. This would cause failures to match multibyte characters against some regular expressions, especially those including the '.' or '\p' metacharacters. ** New features grep -P can now use a just-in-time compiler to greatly speed up matches, This feature is transparent to the user; no flag is required to enable it. It is only available if the corresponding support in the PCRE library is detected when grep is compiled. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.35 2013/05/31 12:42:07 wiz Exp $ d3 1 a3 1 DISTNAME= grep-2.15 @ 1.35 log @Bump all packages for perl-5.18, that a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.34 2012/12/31 00:27:37 sbd Exp $ d3 1 a3 2 DISTNAME= grep-2.14 PKGREVISION= 2 @ 1.34 log @Use ${PKGGNUDIR} and ${PKGMANDIR} in INSTALLATION_DIRS. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.33 2012/12/18 12:08:25 tron Exp $ d4 1 a4 1 PKGREVISION= 1 @ 1.33 log @Mention that this also licensed under later versions as 3 of the GNU GPL. Pointed out by Snader_LB. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.32 2012/12/06 11:43:24 jperkin Exp $ d23 1 a23 1 INSTALLATION_DIRS= gnu/bin gnu/man/man1 @ 1.32 log @Add PKGGNUDIR support. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.31 2012/10/25 06:55:51 asau Exp $ d12 1 a12 1 LICENSE= gnu-gpl-v3 @ 1.31 log @Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.30 2012/10/03 21:57:48 wiz Exp $ d25 2 d28 5 a32 5 .for g n in bin/ggrep gnu/bin/grep bin/gegrep gnu/bin/egrep \ bin/gfgrep gnu/bin/fgrep \ man/man1/ggrep.1 gnu/man/man1/grep.1 \ man/man1/ggrep.1 gnu/man/man1/egrep.1 \ man/man1/ggrep.1 gnu/man/man1/fgrep.1 @ 1.30 log @Bump all packages that use perl, or depend on a p5-* package, or are called p5-*. I hope that's all of them. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.29 2012/08/21 18:04:58 adam Exp $ a13 2 PKG_DESTDIR_SUPPORT= user-destdir @ 1.29 log @Changes 2.14: ** Bug fixes grep -i '^$' could exit 0 (i.e., report a match) in a multi-byte locale, even though there was no match, and the command generated no output. E.g., seq 2 | LC_ALL=en_US.utf8 grep -il '^$' would mistakenly print "(standard input)". Related, seq 9 | LC_ALL=en_US.utf8 grep -in '^$' would print "2:4:6:8:10:12:14:16" and exit 0. Now it prints nothing and exits with status of 1. [bug introduced in grep-2.6] 'grep' no longer falsely reports text files as being binary on file systems that compress contents or that store tiny contents in metadata. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.28 2012/08/03 13:07:54 adam Exp $ d4 1 @ 1.28 log @Changes 2.13: ** Bug fixes grep -i, in a multi-byte locale, when matching a line containing a character like the UTF-8 Turkish I-with-dot (U+0130) (whose lower-case representation occupies fewer bytes), would print an incomplete output line. Similarly, with a matched line containing a character (e.g., the Latin capital I in a Turkish UTF-8 locale), where the lower-case representation occupies more bytes, grep could print garbage. [bug introduced in grep-2.6] --include and --exclude can again be combined, and again apply to the command line, e.g., "grep --include='*.[ch]' --exclude='system.h' PATTERN *" again reads all *.c and *.h files except for system.h. [bug introduced in grep-2.6] ** New features 'grep' without -z now treats a sparse file as binary, if it can easily determine that the file is sparse. ** Dropped features Bootstrapping with Makefile.boot has been broken since grep 2.6, and was removed. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.27 2012/06/01 19:47:46 cheusov Exp $ d3 1 a3 1 DISTNAME= grep-2.13 @ 1.27 log @ Add symlinks in gnu/man/man1/ ++pkgrevision @ text @d1 1 a1 2 # $NetBSD: Makefile,v 1.26 2012/05/29 22:10:24 cheusov Exp $ # d3 1 a3 2 DISTNAME= grep-2.5.3 PKGREVISION= 3 d6 1 a6 1 EXTRACT_SUFX= .tar.bz2 d15 3 a17 1 GNU_CONFIGURE= YES d19 2 a20 2 USE_PKGLOCALEDIR= YES USE_TOOLS+= makeinfo msgfmt a22 1 CONFIGURE_ENV+= MKDIR_P=${INSTALL_DATA_DIR:Q} a25 2 CONFIGURE_ARGS+= --program-prefix=g @ 1.26 log @ Remove GNU_PROGRAM_PREFIX variable (discussed in pkgsrc-users@@). All utilities are installed with a prefix 'g'. Symlinks with original names are created in ${PREFIX}/gnu/bin. ++pkgrevision Add LICENSE @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.25 2011/04/22 13:44:49 obache Exp $ d5 1 a5 1 PKGREVISION= 2 d25 1 a25 1 INSTALLATION_DIRS= gnu/bin d30 6 a35 2 .for p in grep egrep fgrep ln -s ../../bin/g${p} ${DESTDIR}${PREFIX}/gnu/bin/${p} @ 1.25 log @recursive bump from gettext-lib shlib bump. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.24 2008/03/08 12:16:43 tnn Exp $ d5 1 a5 1 PKGREVISION= 1 d13 1 d21 1 a21 1 INFO_FILES= # PLIST d25 1 a25 1 .include "../../mk/bsd.prefs.mk" d27 6 a32 5 .if defined(GNU_PROGRAM_PREFIX) CONFIGURE_ARGS+= --program-prefix=${GNU_PROGRAM_PREFIX:Q} .endif PLIST_SUBST+= GNU_PROGRAM_PREFIX=${GNU_PROGRAM_PREFIX:Q} BUILD_DEFS+= GNU_PROGRAM_PREFIX @ 1.24 log @Update to grep-2.5.3. Main changes are move to GPLv3 and several updated translations. Also some bugfixes (at least the ones we had patched in pkgsrc). Sorry, not more specific because NEWS isn't properly maintained. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.23 2006/04/13 18:23:38 jlam Exp $ d5 1 @ 1.23 log @BUILD_USE_MSGFMT and USE_MSGFMT_PLURALS are obsolete. Replace with USE_TOOLS+=msgfmt. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.22 2006/04/07 19:54:17 jlam Exp $ d4 1 a4 2 DISTNAME= grep-2.5.1 PKGREVISION= 4 d13 2 a14 1 USE_PKGLOCALEDIR= YES a15 1 d17 1 a17 1 d19 1 d21 1 a21 1 INFO_FILES= # PLIST @ 1.22 log @List info files directly in the PLIST and honor PKG{INFO,MAN}DIR. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.21 2006/03/05 16:27:28 jlam Exp $ a14 1 BUILD_USES_MSGFMT= YES d19 1 a19 1 USE_TOOLS+= makeinfo @ 1.21 log @* Teach the tools framework how to supply the pkgsrc version of makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.20 2006/02/05 23:11:02 joerg Exp $ d22 1 a22 1 INFO_FILES= grep.info @ 1.20 log @Recursive revision bump / recommended bump for gettext ABI change. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.19 2005/12/05 23:55:20 rillig Exp $ d20 1 a20 1 USE_MAKEINFO= YES @ 1.19 log @Ran "pkglint --autofix", which corrected some of the quoting issues in CONFIGURE_ARGS. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.18 2005/12/05 20:51:03 rillig Exp $ d5 1 a5 1 PKGREVISION= 3 @ 1.18 log @Fixed pkglint warnings. The warnings are mostly quoting issues, for example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.17 2005/04/11 21:47:34 tv Exp $ d27 1 a27 1 CONFIGURE_ARGS+= --program-prefix=${GNU_PROGRAM_PREFIX} @ 1.17 log @Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.16 2004/10/03 00:18:19 tv Exp $ d29 1 a29 1 PLIST_SUBST+= GNU_PROGRAM_PREFIX=${GNU_PROGRAM_PREFIX} @ 1.16 log @Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.15 2004/04/25 05:03:43 snj Exp $ a13 1 USE_BUILDLINK3= YES @ 1.15 log @Convert to buildlink3. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.14 2004/02/09 08:13:04 grant Exp $ d5 1 a5 1 PKGREVISION= 2 @ 1.14 log @bsd.pkg.mk now runs GNU configure scripts with ${SH}, so we no longer need to do so here. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.13 2003/09/18 19:13:50 wiz Exp $ d14 1 a14 1 USE_BUILDLINK2= YES d33 1 a33 1 .include "../../devel/gettext-lib/buildlink2.mk" @ 1.13 log @Update to 2.5.1nb2: Use the right grep binary in fgrep and egrep shell scripts. Patch provided by Nicolas Fugier in PR 20905. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.12 2003/08/09 11:27:48 seb Exp $ a32 4 .if ${OPSYS} == "SunOS" CONFIGURE_SCRIPT= ${SH} ./configure .endif @ 1.12 log @USE_NEW_TEXINFO is unnecessary now. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.11 2003/08/02 05:19:57 grant Exp $ d5 1 a5 1 PKGREVISION= 1 @ 1.11 log @use new texinfo handling. minor whitespace fix. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.10 2003/07/30 17:00:04 grant Exp $ a20 1 USE_NEW_TEXINFO= YES @ 1.10 log @explicitly disable pcre support as it was never enabled. fixes build on systems which have libpcre installed as the configure script's detection of it is slightly broken. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.9 2003/07/17 22:54:16 grant Exp $ d14 1 a14 1 USE_BUILDLINK2= YES a16 2 TEXINFO_REQD= 4.0 d21 5 a38 1 .include "../../mk/texinfo.mk" @ 1.9 log @s/netbsd.org/NetBSD.org/ @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.8 2003/07/13 13:53:32 wiz Exp $ d20 2 @ 1.8 log @PKGREVISION bump for libiconv update. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.7 2003/06/24 05:29:06 grant Exp $ d10 1 a10 1 MAINTAINER= bouyer@@netbsd.org @ 1.7 log @remove unneeded parens, quote a literal in .if @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.6 2003/02/13 07:33:34 wiz Exp $ d5 1 @ 1.6 log @Update to 2.5.1: bugfix release. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.5 2003/01/09 17:23:10 cjep Exp $ d28 1 a28 1 .if (${OPSYS} == SunOS) @ 1.5 log @USE_PKGLOCALEDIR=yes. Fixes PLIST problems on SunOS @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.4 2002/12/25 19:54:58 wiz Exp $ d4 1 a4 1 DISTNAME= grep-2.5 @ 1.4 log @Use .tar.bz2. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.3 2002/12/25 19:50:34 wiz Exp $ d14 1 @ 1.3 log @Honor GNU_PROGRAM_PREFIX, patch by Jeremy C. Reed. While here: Fix build on NetBSD-current. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.2 2002/12/06 15:29:20 cjep Exp $ d7 1 @ 1.2 log @Fix up configure nit for Solaris. Suggested by tron. @ text @d1 2 a2 2 # $NetBSD: Makefile,v 1.1.1.1 2002/10/14 16:43:14 bouyer Exp $ # FreeBSD Id: Makefile,v 1.10 1999/01/27 07:41:16 fenner Exp $ d16 1 a16 2 GNU_CONFIGURE= yes CONFIGURE_ARGS+= --program-prefix=g d19 6 @ 1.1 log @Initial revision @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.2 1999/06/08 09:27:27 sakamoto Exp $ d18 6 @ 1.1.1.1 log @Package for GNU grep 2.5. @ text @@