[oe] [meta-browser] RFC: updating chromium-ozone-wayland to 65.0.xxxx.0.rxxxxxx.igalia.1

Andrey Konovalov andrey.konovalov at linaro.org
Tue Jan 23 14:16:24 UTC 2018


Hello Maksim,

On 23.01.2018 15:52, Maksim Sisov wrote:
> Hello Andrey,
> 
> Yes, it makes sense to update the recipe, which I'm going to do in the
> end of this or in the beginning of the next week,

That's great news!

Thanks,
Andrey

> as long as the work is
> based on chromium ToT, and the code base is always changing.
> 
> On 22.01.2018 21:54, Andrey Konovalov wrote:
>> Hello,
>>
>> chromium-ozone-wayland_64.0.3274.0.r517731.igalia.1.bb from current
>> meta-browser [1] didn't
>> quite worked for me: e.g. I was getting the "Aw Snap" after filling in
>> the search text box and pressing <Enter>
>> at youtube.com; sometimes when moving the mouse pointer over the
>> screen the mouse cursor became the arrow
>> and was not changing for quite a while when moving over the chromium
>> window (looks similar to the issue [2]
>> though it should have been fixed in r517731 if I got it correct).
>>
>> But when I tried updating chromium-ozone-wayland to version 65 using
>> [3] as the basis,
>> those two issues were gone, and chromium became much more usable for
>> me. Then I did the following:
>>    * from [3] took only the changes relevant to the version update,
>>    * rebased on the current OSSystems/meta-browser,
>>    * replaced the patches added to SRC_URI with the upstream versions
>> where applicable,
>>    * updated to the latest tarball at [4] (though I don't see a
>> difference in how 65.0.3298.0.r524623
>>      and 65.0.3315.0.r527534 behave, any of these are OK for me)
>> - thus ending up with [5] (the 3 topmost commits).
>> (If we go with r524623, the topmost commit is to be dropped. Or if we
>> go with r527534, the two topmost commits
>> are to be squashed into one.)
>> Basically this is still the subset of Maxim's work [3] with minor changes.
>>
>> Does it make sense to update chromium-ozone-wayland to version 65 now?
>> One of my concerns is that it was only tested on an aarch64 target
>> (dragonboard-410c) in rocko, and build-only-tested
>> for an armv7 machine (am57xx-evm, rocko as well).
>>
>>
>> Thanks,
>> Andrey
>>
>>
>> [1]
>> https://github.com/OSSystems/meta-browser/tree/master/recipes-browser/chromium
>> [2] https://github.com/Igalia/chromium/issues/317
>> [3]
>> https://github.com/Igalia/meta-browser/commits/ozone/wayland/65.0.3298.0.r524623
>> [4] https://tmp.igalia.com/chromium-tarballs/
>> [5] https://github.com/andrey-konovalov/meta-browser/commits/my.master
> 
> -Maksim
> 




More information about the Openembedded-devel mailing list