| 1 |
On Tuesday 23 Jun 2015 11:54:02 Neil Bothwick wrote: |
| 2 |
> On Tue, 23 Jun 2015 05:26:31 -0500, Dale wrote: |
| 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 |
> > Thanks. That was what I was looking for. I guess they did do this |
| 8 |
> > then. This may be the first time I checked into a story from that site |
| 9 |
> > and it be true. It seems google did sort of sneak some code in there. |
| 10 |
> > o_O |
| 11 |
> |
| 12 |
> There is a now a USE flag to specifically enable this. It defaults to |
| 13 |
> disabled but if you previously emerged chromium before the flag as added, |
| 14 |
> you will still have it. Using --newuse will cause a world update to |
| 15 |
> re-emerge chromium, but if you use --changed-use it doesn't, so re-emerge |
| 16 |
> chromium if you want to get rid of this. |
| 17 |
|
| 18 |
What is the new USE flag and does it also apply to 43.0.2357.65? |
| 19 |
|
| 20 |
-- |
| 21 |
Regards, |
| 22 |
Mick |
Archives