| 1 |
El mié, 06-06-2012 a las 13:23 -0400, Mike Frysinger escribió: |
| 2 |
> On Wednesday 06 June 2012 04:26:11 Pacho Ramos wrote: |
| 3 |
> > I think that would be interesting to try to not get grep build with pcre |
| 4 |
> > support by default, specially after reading "man grep" and seeing that |
| 5 |
> > its support is tagged as experimental: |
| 6 |
> > -P, --perl-regexp |
| 7 |
> > Interpret PATTERN as a Perl regular expression. This is |
| 8 |
> > highly |
| 9 |
> > experimental and grep -P may warn of unimplemented |
| 10 |
> > features. |
| 11 |
> |
| 12 |
> the experimental aspect doesn't matter. don't use -P and it isn't an issue. |
| 13 |
> |
| 14 |
> personally, i don't care about pcre. |
| 15 |
> -mike |
| 16 |
|
| 17 |
The problem is that grep keeps linked against libpcre and it can cause |
| 18 |
problems like pointed in referred bug report, and it's really risky as |
| 19 |
people can have their portage completely broken for example when libpcre |
| 20 |
is downgraded for some reason. That doesn't sound like a good *default* |
| 21 |
behavior for me |
| 22 |
|
| 23 |
Of course, other option would be to default to "-pcre" for grep only (by |
| 24 |
default), but I don't know if we really want every package to have pcre |
| 25 |
by default... |
Archives