Package: grep
Version: 2.12-2
Severity: important
Apparently grep -r and rgrep no longer follow symlinks whereas grep -R
still does:
% echo foo > file1 ; ln -s file1 file2
% grep -r foo .
./file1:foo
% grep -R foo .
./file2:foo
./file1:foo
%
This change of behaviour is not documented in the manpage, which still
claims that -r and -R do the same thing:
-R, -r, --recursive
Read all files under each directory, recursively; this is
equivalent to the -d recurse option.
This change breaks existing scripts which rely on "grep -r" reporting
about symbolic links to files, too.
Regardless of the merits of the change, it also breaks compatibility
with BSD grep. I don't think we can accept that.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grep depends on:
ii dpkg 1.16.4.2
ii install-info 4.13a.dfsg.1-10
ii libc6 2.13-33
grep recommends no packages.
Versions of packages grep suggests:
ii libpcre3 1:8.30-5
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
