On 23/05/2019 17.19, Jan-Marek Glogowski wrote:
IMHO that leaves us with:
1. don't allow to load the qt5 plugin in 6.2 at all
2. switch qt5 to cairo in 6.2 only
3. cope with the eventual bug fallout, when 6.2 becomes still (which I think
won't be large, but who knows)
Honestly I would go with 3. Eventually even 2.
Sounds reasonable to me (both, 3. and 2.).
P.S. and if kde5 doesn't make it into still, qt5 will be gone too.
That depends. My understanding of the discussion so far (s.a.
tdf#124044) was that kde5 wouldn't be the default (on Plasma/LXQt) if
not considered "ready" in time for 6.2.5. This could e.g. easily be
achieved by reverting commit f2bf002e90bf5cc74cf190d66507e59b78ba73e9
("Add autodetection for KDE5 VCL Plugin").
In this case, people manually setting "SAL_USE_VCLPLUGIN" would still be
able to choose qt5 or kde5, but IMHO people doing so should know what
they're doing... (matching case 3 from above).
I don't have strong opinion on that, though.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.