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 "man grep" and seeing that > > its support is tagged as experimental: > > This is more a reason to mask USE=pcre for grep, rather than taking > global action, where pcre may have different meaning or status for other > packages. >
I thought about that option at first time, but later I checked grep ChangeLog and saw "pcre" USE flag was dropped time ago but later readded due user request. > > Also, at least of my systems there are only a few installed packages > > with this USE flag and, then, I am unsure about real advantage of having > > it enabled by default :-/ > > This is a possible reason for dropping it, but I'm not sure. What > exactly uses it and why? > > Paweł > In my laptop, just now, only a few: $ equery hasuse pcre * Searching for USE flag pcre ... [IP-] [ ] app-admin/syslog-ng-3.2.5:0 [IP-] [ ] dev-lang/swig-2.0.4-r1:0 [IP-] [ ] dev-libs/rasqal-0.9.28:0 [IP-] [ ] sys-apps/grep-2.9:0 but running it with "-p" shows me there are a lot that I don't know if their support deserves to be enabled by default :(
signature.asc
Description: This is a digitally signed message part
