PF4Public

I'm afraid, you'll have to give up on those flags. Google constantly introduces tricky to untangle dependencies there.

@blackteahamburger Have you tried the latest electron? I think I've back-ported latest av1 and vpx patches from Chromium.

> I found a lot of imperfections in the ebuilds in this repository :D Like I mentioned in another issue here, I value maintainability more than perfection. Especially that I...

> > > add .gitignore > > > > > > This file does not belong here > > For convenience for pkgcheck. Overlays I know all have it. you...

> > > > > add .gitignore > > > > > > > > > > > > This file does not belong here > > > > >...

> add `chromium-117-material-color-include.patch` (still needed?). > > > > I don't think it is needed anymore: https://source.chromium.org/chromium/chromium/src/+/main:third_party/material_color_utilities/src/cpp/palettes/tones.cc;drc=13434b50dcb64a482cc91191f8cf6151d90f5465;l=19 > I don't know the reason but just consider that it was there...

> Should be OK with NODIE check. NODIE is set in GitHub runner, therefore it will fail there, that's what I was trying to avoid. > What's more interesting is...

> You could consider asking upstream I'm not asking anyone, I decide for myself!

> You may have misunderstood what I meant because I didn't ask you to actually ask. Sorry > After testing, I unfortunately noticed that it has no effect when thinlto-jobs...

> Removing `-Wl,--thinlto-jobs=$(makeopts_jobs)` is just fine. This would break the expectation associated with MAKEOPTS, I'm not eager to do so.