I reverted the change as it breaks Leap 42 and revoked the sr to TW. Please resubmit/reopen if you can list a package which requires this to work and also keep it enabled for Leap 42.
Qt 4 has reached EOL. I do not want to enable additional functionality on something that's officially unmaintained. I second Fabian's question: what do you need this for?
The API of mariadb will change at some point in a way which breaks Qt 4 anyway. It's important to not include any new dependencies on legacy components.
Does anything require this?
It was intentionally disabled and I don't see a reason to enable it again.
Is there a downside to enabling this though?
Yes, more legacy code we would not want to see in the distribution IMO.
This is actually more broken than I thought - this disables the plugin for Leap 42.
I reverted the change as it breaks Leap 42 and revoked the sr to TW. Please resubmit/reopen if you can list a package which requires this to work and also keep it enabled for Leap 42.
Wy revert?. I need it for my package. And nothing is broken. People who not need it, must not install it. What will broken?
Which package do you need it for? Qt4 is legacy.
It broke building for Leap.
Qt 4 has reached EOL. I do not want to enable additional functionality on something that's officially unmaintained. I second Fabian's question: what do you need this for?
I build it without problems.
Yes Qt4 has reached EOL. But a package need it. And the mysql plugin was enabled in Leap 42.3. It is disabled since Leap 15.
I dont't understand why only mysql-plugin is disabled. And i think many other packages still need qt4.
The API of mariadb will change at some point in a way which breaks Qt 4 anyway. It's important to not include any new dependencies on legacy components.
Which package needs it?