1 |
On Tue, 23 Jun 2015 05:26:31 -0500, Dale wrote: |
2 |
|
3 |
> > Take from that what you will. Note, the issues are for chromium and |
4 |
> > not for Google Chrome, shouldn't make a difference for what you want |
5 |
> > to know though. |
6 |
> > |
7 |
> |
8 |
> Thanks. That was what I was looking for. I guess they did do this |
9 |
> then. This may be the first time I checked into a story from that site |
10 |
> and it be true. It seems google did sort of sneak some code in there. |
11 |
> o_O |
12 |
|
13 |
There is a now a USE flag to specifically enable this. It defaults to |
14 |
disabled but if you previously emerged chromium before the flag as added, |
15 |
you will still have it. Using --newuse will cause a world update to |
16 |
re-emerge chromium, but if you use --changed-use it doesn't, so re-emerge |
17 |
chromium if you want to get rid of this. |
18 |
|
19 |
|
20 |
-- |
21 |
Neil Bothwick |
22 |
|
23 |
Time is an illusion but never so much as when you're using a modem. |