[Webkit-unassigned] [Bug 146680] Replace OpenGL{, ES}Shims with libepoxy, and #if USE(OPENGL_ES_2) with runtime checks

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=146680

--- Comment #11 from Carlos Garcia Campos <cgarcia at igalia.com> ---
(In reply to comment #8)
> (In reply to comment #5)
> > libepoxy is a small library, we could also add it to ThirdParty if adding
> > the dependency would be a problem
> 
> GTK+ already depended on libepoxy (since 3.18 i believe). So it will not be
> a real new dependency at least for WebKitGTK+. But I understand the concern
> for other ports. Would this patch implement something that will be used for
> WebKitGTK+ or it will be shared with other ports?

It's a real dependency as long as we still support older versions of GTK+. It will be shared.

> GTK+ depends on libepoxy.(In reply to comment #6)
> > (In reply to comment #5)
> > > libepoxy is a small library, we could also add it to ThirdParty if adding
> > > the dependency would be a problem
> > 
> > I think that would be better than adding a new dependency, which I think is
> > something that the policy didn't cover.
> 
> Well, my reading of the policy is that is ok to add a new dependency
> meanwhile at least one of this two preconditions is true:
> 
>  - The dependency is needed for building WebKitGTK+ and Debian/Ubuntu
> already ships that dependency. The policy is : "WebKitGTK+ should be
> build-adble on the last Ubuntu LTS and last Debian stable" + 1 year since a
> new Debian/UbuntuLTS is released.
>  - The dependency is optional (ex: it is needed for some feature that can be
> disabled)
> 
> But we should clarify this.. do you think is worth raising the topic another
> time on the mailing list?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160906/1b724726/attachment.html>