Package Details: qt4 4.8.7-35

Git Clone URL: https://aur.archlinux.org/qt4.git (read-only, click to copy)
Package Base: qt4
Description: A cross-platform application and UI framework
Upstream URL: https://www.qt.io
Licenses: custom, GPL3, LGPL, FDL
Conflicts: qt
Replaces: qt
Submitter: arojas
Maintainer: dviktor
Last Packager: dviktor
Votes: 74
Popularity: 1.68
First Submitted: 2019-05-01 11:51 (UTC)
Last Updated: 2022-05-13 12:03 (UTC)

Sources (22)

Pinned Comments

dviktor commented on 2022-09-28 18:33 (UTC)

PKGBUILD for this package is being maintained there. You can install pre-built packages from my repo

dviktor commented on 2019-06-18 12:50 (UTC) (edited on 2022-01-27 12:28 (UTC) by dviktor)

Qt4 binary package has moved to my personal repository located here. You can add it to your /etc/pacman.conf for convenience, if you want (don't forget to import my GPG key).

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 declared error: build in clean chroot with extra-x86_64-build script.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 Next › Last »

piedro commented on 2019-05-10 11:54 (UTC)

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

Tharbad commented on 2019-05-10 03:24 (UTC)

Getting ‘std::tr1’ has not been declared despite building in clean chroot

dviktor commented on 2019-05-09 23:53 (UTC) (edited on 2019-05-10 10:28 (UTC) by dviktor)

@deemoncheeque did you download the whole snapshot or just PKGBUILD?

deemoncheeque commented on 2019-05-09 18:01 (UTC)

I'm building the package in clean chroot and it fails with one or more PCH files were found, but they were invalid. What to do with it now? Bin: https://pastebin.com/iNzDFYxq

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.

semeion commented on 2019-05-08 20:02 (UTC)

@piedro, I really think qt4 should be moved to mainline repo ... a lot of work to compile something used by multiple applications that are in the mainline repo.

piedro commented on 2019-05-08 17:49 (UTC)

Is this becessary in any way? I mean, is there a problem using the older version?

This compiling doesn't work and setting up another environment just to compile it seems a bit over the top imho...

Also, is there a binary to use somewhere?

thx, p.

dviktor commented on 2019-05-08 10:39 (UTC) (edited on 2019-05-08 14:44 (UTC) by dviktor)

@saverio please, download the whole snapshot, not only pkgbuild itself

saverio commented on 2019-05-08 10:37 (UTC)

I tried to build from qt4 (PKGBUILD), but I receive this error during pakages downloading...

==> Making package: qt4 4.8.7-29 (mer 8 mag 2019, 12:34:19) ==> Retrieving sources... -> Downloading qt-everywhere-opensource-src-4.8.7.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 274 100 274 0 0 948 0 --:--:-- --:--:-- --:--:-- 948 100 229M 100 229M 0 0 7662k 0 0:00:30 0:00:30 --:--:-- 5647k ==> ERROR: qtconfig-qt4.desktop was not found in the build directory and is not a URL. ==> ERROR: Could not download sources.

dviktor commented on 2019-05-07 17:10 (UTC)

@semeion this package was removed from official repos and uploaded here. you can set up clean chroot as described here

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 Next › Last »