On Fri, Nov 23, 2018 at 12:25:51PM +0100, Julien Cristau wrote: > > According to config_help.txt [1], Qt uses ES2 by default on Windows. > > It probably means that it will work fine with most desktop video cards. > > > > But as Lisandro says, such a change in Debian will break many packages > > (which are currently broken on ARM only), so we are definitely not > > considering it at this point. > > Why is it OK to break them on arm64 if it's not OK to break them on > amd64? Do you have a list of those packages? The majority of arm64 devices are mobile/embedded, which cannot be said about amd64. Of course it is bad to break packages, but leaving arm64 users with non-working Qt graphics is also not ideal. So we are trying to find a compromise solution here. We do not have a final list yet, but packages that may get broken will likely belong to one of these two groups: - Packages that build-depend on both qtbase5-dev and libglu1-mesa-dev: cgal, flightgear, fraqtive, kalgebra, kstars, ksudoku, kubrick, paraview, simplescreenrecorder, starpu, starpu-contrib, structure-synth, vtk6, vtk7 - Packages that build-depend on libqt5opengl5-desktop-dev: bino, deepin-movie-reborn, enki-aseba, fracplanet, fraqtive, freecad, krita, libconfig-model-dpkg-perl, mldemos, mm3d, openms, qwtplot3d, shelxle, soundscaperenderer, tetzle, virtualjaguar, vite, vtk7 This is not a final list yet, but should be enough to get an estimate. -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature