Re: Upcoming Qt switch to OpenGL ES on arm64
- Date: Sat, 24 Nov 2018 20:07:40 +0200
- From: Adrian Bunk <bunk@xxxxxxxxxx>
- Subject: Re: Upcoming Qt switch to OpenGL ES on arm64
On Sat, Nov 24, 2018 at 02:40:37PM +0100, Matthias Klose wrote:
> On 24.11.18 11:26, Andy Simpkins wrote:
> >> So, again: which of the two flavors is the one that benefits more of our user
> >> base?
> > BOTH are possible so why dictate only one?
> > I would like to see OpenGLES available on all architectures
> > I would like to see OpenGL available on all architectures
> > I think that there is a relatively painless method to achieve this
> > I believe this would also meet your needs
> so why not keep GL as it is now, and build the GLES packages from a single
> source tarball? This way you minimize your uploads while having both
> implementations in the archive? Maybe later on, you could even do the same for
> the 32bit ARM architectures if these are still release architectures by that time.
Putting all KDE packages plus all other Qt-using packages into one
monster source tarball for building them a second time sounds like
a nightmare impossible to maintain.
Like how would security updates of gst-plugins-good1.0 in stable work
when a second copy of it is in the monster tarball due to gstreamer1.0-qt5?
libqt5gui5 has > 1k rdeps, the sanest way forward for providing two
different ABI versions of libqt5gui5 at the same time would be two
architectures for arm64.
And that is not a realistic option.
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed