The package "sip" is in the official extra repository and still needs qt4.
Also "everpad", "soundwire", "spflashtool"... to name only a few.
The idea to "dry the well" to make people behave in a certain way seems very questionable to me... The decision to make it harder for users in order to force porting is really twisted! And also misdirected. The result is that the users waste their time on figuring out how to compile qt4 while the developers of the "old" applications just don't care...
But well, though I am not a developer responsible for porting to qt5 I still need qt4 - so I will have to figure out how to compile it. What a waste of time.
pk
Pinned Comments
eschwartz commented on 2019-05-09 13:24 (UTC)
@semeion,
qt4 was expelled from the official repositories due to https://lists.archlinux.org/pipermail/arch-dev-public/2019-April/029560.html
It will not be restored, because software needs to stop using qt4. It's fine for people to still use it via the AUR if they have old software that is not ported, but the proper solution is to get that software ported to qt5.
"It takes a long time to compile" is not a reason to move it to community.
@xuanruiqi,
Only Developers and Trusted Users have access to pkgbuild.com, and we will not be uploading qt4 there. If we wanted qt4, we would upload it to community, but we don't -- we have managed to move every package still being actively maintained in the official repos, over to qt5, and we want to stay that way.
...
Again, the proper long-term solution is to get software ported over to qt5.
dviktor commented on 2019-05-05 17:49 (UTC) (edited on 2019-05-15 19:02 (UTC) by dviktor)
For those who have problems with
‘std::tr1’ has not been declarederror: build in clean chroot withextra-x86_64-buildscript.