| 1 |
Mick wrote: |
| 2 |
> On Tuesday 23 Jun 2015 11:54:02 Neil Bothwick wrote: |
| 3 |
>> On Tue, 23 Jun 2015 05:26:31 -0500, Dale wrote: |
| 4 |
>>>> Take from that what you will. Note, the issues are for chromium and |
| 5 |
>>>> not for Google Chrome, shouldn't make a difference for what you want |
| 6 |
>>>> to know though. |
| 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 |
> What is the new USE flag and does it also apply to 43.0.2357.65? |
| 20 |
> |
| 21 |
|
| 22 |
|
| 23 |
https://code.google.com/p/chromium/issues/detail?id=491435 |
| 24 |
|
| 25 |
It's mentioned in post 4 first. I don't know if Gentoo is using the |
| 26 |
same name or not tho. It should be a start at least. |
| 27 |
|
| 28 |
Dale |
| 29 |
|
| 30 |
:-) :-) |
Archives