[aur-general] qt4 replaces qt
Hi all, a new qt4 package has hit [testing] and will replace the current qt package. qt4 doesn't provide 'qt'; you will need to rebuild EVERY package installed from AUR and replace qt with qt4 in the depends array. Also, I suggest to every maintainer in AUR to remove qt from the depends() array when there's qtwebkit or any package that needs qt: if you do that, this will require no rebuild as we updated every package in the official repositories to use qt4. Also, we ship the Qt 5.x series in [testing]. Qt 5.x is more modular than 4.x. This allow us to have these Qt 5.x packages: * qt5-base * qt5-declarative * qt5-graphicaleffects * qt5-imageformats * qt5-jsbackend * qt5-multimedia * qt5-quick1 * qt5-script * qt5-svg * qt5-tools * qt5-translations * qt5-webkit * qt5-xmlpatterns Generally you only need qt5-base. But, if you are a Qt developer or you want a full installation you can install the whole 'qt' group. When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4. -- Andrea Arch Linux Developer
On Wednesday 27 February 2013 16:21:24 you wrote:
When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4.
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options Cheers -- Andrea Arch Linux Developer
On 2013年02月28日 07:14, Andrea Scarpino wrote: > On Wednesday 27 February 2013 16:21:24 you wrote: >> When you install both qt5-base and qt4, qmake will refers to the 5.x >> version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also >> moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used >> by cmake and by the configure scripts to locate qt4. > Please maintainers fix your PKGBUILDs so they build on systems with both qt4 > and qt5-base installed; when your PKGBUILD needs qt4 and: > * use qmake, you can replace it with qmake4 > * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options > > Cheers > Can this (replace all qt with qt4) be done automatically by some script on the AUR server ?
On Wed, Feb 27, 2013 at 6:14 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Wednesday 27 February 2013 16:21:24 you wrote:
When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4.
This should probably be done for all package that links to qt including those that are not directly depending on qt.
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options
Cheers
-- Andrea Arch Linux Developer
On Wed, Feb 27, 2013 at 10:19 PM, Yichao Yu <yyc1992@gmail.com> wrote:
On Wed, Feb 27, 2013 at 6:14 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Wednesday 27 February 2013 16:21:24 you wrote:
When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4.
This should probably be done for all package that links to qt including those that are not directly depending on qt.
After testing the current kde PKGBUILD's (by felixonmars), it is clear that any package that links to qt need to change their PKGBUILD if the situation is not changing. Especially ALL kde packages (well probably not including wallpapers etc....)
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options
Cheers
-- Andrea Arch Linux Developer
On Wed, Feb 27, 2013 at 10:37 PM, Yichao Yu <yyc1992@gmail.com> wrote:
On Wed, Feb 27, 2013 at 10:19 PM, Yichao Yu <yyc1992@gmail.com> wrote:
On Wed, Feb 27, 2013 at 6:14 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Wednesday 27 February 2013 16:21:24 you wrote:
When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4.
This should probably be done for all package that links to qt including those that are not directly depending on qt.
After testing the current kde PKGBUILD's (by felixonmars), it is clear that any package that links to qt need to change their PKGBUILD if the situation is not changing. Especially ALL kde packages (well probably not including wallpapers etc....)
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options
And good luck for all developers using Qt, don't forgot to run cmake with this flag after the upgrade.
Cheers
-- Andrea Arch Linux Developer
On Wednesday 27 February 2013 22:37:01 Yichao Yu wrote:
After testing the current kde PKGBUILD's (by felixonmars), it is clear that any package that links to qt need to change their PKGBUILD if the situation is not changing. Especially ALL kde packages (well probably not including wallpapers etc....)
Yes, we did and we do this with the python2 packages too, adding PYTHON=/usr/bin/python2 before the configure call. -- Andrea Arch Linux Developer
On Thursday 28 February 2013 00:14:55 you wrote:
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options
qt4 is in [extra], please AUR maintainers fix your packages! Thanks. -- Andrea Arch Linux Developer
On Fri, Mar 1, 2013 at 11:20 AM, Andrea Scarpino <andrea@archlinux.org> wrote:
qt4 is in [extra], please AUR maintainers fix your packages!
I'm commenting packages that use qt one by one now. Will there be an automatic message sent to packages that depend on qt?
On Fri, Mar 1, 2013 at 2:35 PM, SanskritFritz <sanskritfritz@gmail.com> wrote:
On Fri, Mar 1, 2013 at 11:20 AM, Andrea Scarpino <andrea@archlinux.org> wrote:
qt4 is in [extra], please AUR maintainers fix your packages!
I'm commenting packages that use qt one by one now. Will there be an automatic message sent to packages that depend on qt?
Ah, an announcement on the front page. That works too :) Thanks!
On 2013-03-01 22:59 +0100 SanskritFritz wrote:
On Fri, Mar 1, 2013 at 2:35 PM, SanskritFritz <sanskritfritz@gmail.com> wrote:
On Fri, Mar 1, 2013 at 11:20 AM, Andrea Scarpino <andrea@archlinux.org> wrote:
qt4 is in [extra], please AUR maintainers fix your packages!
I'm commenting packages that use qt one by one now. Will there be an automatic message sent to packages that depend on qt?
Ah, an announcement on the front page. That works too :) Thanks!
If anyone wants to avoid redundant recompilation of some packages, you can use my "repkg" script: http://xyne.archlinux.ca/scripts/pacman/#repkg What you need: build package, updated PKGBUILD What you do: "repkg <pkgfile>" in directory with updated PKGBUILD Use only with metadata changes.
I am in the process of rebuilding my qt-at-spi-git package now. As it is a necessary package for making qt applications accessible to blind and visually impaired users, I apologize for the rather late rebuild. ~Kyle http://kyle.tk/ -- "Kyle? ... She calls her cake, Kyle?" Out of This World, season 2 episode 21 - "The Amazing Evie"
On Thursday 28 February 2013 00:14:55 you wrote:
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake options
Just a note here: I had to remove the qmake4 symlink and use qmake-qt4 instead as the former was inconsistent with others distro. When I did this change (1th March) qmake4 wasn't really used yet so I did not think to write this mail before. I'm sorry if this caused more confusion here. -- Andrea Arch Linux Developer
2013/3/4 Andrea Scarpino <andrea@archlinux.org>
Please maintainers fix your PKGBUILDs so they build on systems with both qt4 and qt5-base installed; when your PKGBUILD needs qt4 and: * use qmake, you can replace it with qmake4 * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake
On Thursday 28 February 2013 00:14:55 you wrote: options
Just a note here: I had to remove the qmake4 symlink and use qmake-qt4 instead as the former was inconsistent with others distro. When I did this change (1th March) qmake4 wasn't really used yet so I did not think to write this mail before. I'm sorry if this caused more confusion here.
-- Andrea Arch Linux Developer
No matter, a simple "ls" on bin directory can easily show qmake-qt4 instead qmake4, and checking a package before submit it should show that qmake4 doesn't compile, so it is not such a big problem
participants (7)
-
Andrea Scarpino
-
GSC
-
Jorge Barroso
-
Kyle
-
SanskritFritz
-
Xyne
-
Yichao Yu