On Tuesday 23 Jun 2015 11:54:02 Neil Bothwick wrote: > On Tue, 23 Jun 2015 05:26:31 -0500, Dale wrote: > > > Take from that what you will. Note, the issues are for chromium and > > > not for Google Chrome, shouldn't make a difference for what you want > > > to know though. > > > > Thanks. That was what I was looking for. I guess they did do this > > then. This may be the first time I checked into a story from that site > > and it be true. It seems google did sort of sneak some code in there. > > o_O > > There is a now a USE flag to specifically enable this. It defaults to > disabled but if you previously emerged chromium before the flag as added, > you will still have it. Using --newuse will cause a world update to > re-emerge chromium, but if you use --changed-use it doesn't, so re-emerge > chromium if you want to get rid of this.
What is the new USE flag and does it also apply to 43.0.2357.65? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
