Currently https://github.com/anholt/libepoxy unmaintained and have bugs for example: https://bugs.kde.org/show_bug.cgi?id=369317 we must use fork https://github.com/yaronct/libepoxy it is developing and many bug fixes. Reproducible: Always
People were discussing this at XDC. I'll see what the status is.
This yaronct person who forked libepoxy now commits directly to the original repo: https://github.com/anholt/libepoxy/commits/master?author=yaronct Looks like there's no need to switch after all as fork is now lagging behind the original repo: https://github.com/yaronct/libepoxy
To my knowledge who was given access was fixing a lot of win32 stuff, but breaking linux. ebassi was going to consider taking it over or re-forking or something due to GTK+ using it now. I'll also have to check where things stand now.
Meanwhile I don't believe what we have is bad in principle, until something needs some sort of fixes or new API. libepoxy API is very minimal and there's not much to go on really. If there are bugs affecting KDE as linked, maybe for starters we can just do a revision bump with a fix, until things get settled with the forks or whatever.
>now commits directly to the original repo It's nice but currently I can't build kwin with latest libeproxy. With stable libeproxy I have errors in runtime. >If there are bugs affecting KDE as linked, maybe for starters we can just do a revision bump with a fix, until things get settled with the forks or whatever. You intend to maintain project on their own? Martin Gräßlin advised me stop use GLES for KWin, also Intel drivers really in bad state. I think KWin developers must cooperate with libeproxy guys but currently GLSL is not first class citizen in KWin.
Noticed discussion on this today on IRC by the relevant devs: <aboll> ebassi: what's the status of merging your libepoxy fork into anholt's repo? btw thanks for working on libepoxy! <anholt> aboll: yaronct got upset by it, but I think we need to just thank yaronct for his work and move on to ebassi's branch. <ebassi> aboll: I'm going to work on the cross-compilation bits with meson, and see where we stand
media-libs/libepoxy upstream is now maintained https://github.com/anholt/libepoxy. This bug should be closed.
Excellent. Thanks.