After reading:
https://bugs.gentoo.org/show_bug.cgi?id=419795
I think that would be interesting to try to not get grep build with pcre
support by default, specially after reading man grep and seeing that
its support is tagged as experimental:
-P, --perl-regexp
Interpret
On 6/6/12 10:26 AM, Pacho Ramos wrote:
After reading:
https://bugs.gentoo.org/show_bug.cgi?id=419795
I think that would be interesting to try to not get grep build with pcre
support by default, specially after reading man grep and seeing that
its support is tagged as experimental:
This is
El mié, 06-06-2012 a las 10:37 +0200, Paweł Hajdan, Jr. escribió:
On 6/6/12 10:26 AM, Pacho Ramos wrote:
After reading:
https://bugs.gentoo.org/show_bug.cgi?id=419795
I think that would be interesting to try to not get grep build with pcre
support by default, specially after reading
On Wednesday 06 June 2012 04:26:11 Pacho Ramos wrote:
I think that would be interesting to try to not get grep build with pcre
support by default, specially after reading man grep and seeing that
its support is tagged as experimental:
-P, --perl-regexp
Interpret PATTERN
El mié, 06-06-2012 a las 13:23 -0400, Mike Frysinger escribió:
On Wednesday 06 June 2012 04:26:11 Pacho Ramos wrote:
I think that would be interesting to try to not get grep build with pcre
support by default, specially after reading man grep and seeing that
its support is tagged as
On Wednesday 06 June 2012 14:06:47 Pacho Ramos wrote:
The problem is that grep keeps linked against libpcre and it can cause
problems like pointed in referred bug report, and it's really risky as
people can have their portage completely broken for example when libpcre
is downgraded for some
El mié, 06-06-2012 a las 14:53 -0400, Mike Frysinger escribió:
On Wednesday 06 June 2012 14:06:47 Pacho Ramos wrote:
The problem is that grep keeps linked against libpcre and it can cause
problems like pointed in referred bug report, and it's really risky as
people can have their portage
