Arch Linux User Repository

Please consider supporting upstream to keep this project alive.

[ 56%] Building CXX object CMakeFiles/aqemu.dir/Embedded_Display/vncclientthread.o [ 57%] Building CXX object CMakeFiles/aqemu.dir/Embedded_Display/vncview.o In file included from /usr/include/QtGui/qevent.h:57:0, from /usr/include/QtGui/QMouseEvent:1, from /tmp/yaourt-tmp-root/aur-aqemu/src/aqemu-0.8.2/Embedded_Display/vncview.cpp:44: /usr/include/QtCore/qfile.h:117:21: error: macro "error" requires 3 arguments, but only 1 given /usr/include/QtCore/qfile.h:117:15: error: expected ‘;’ at end of member declaration /usr/include/QtCore/qfile.h:117:23: error: declaration does not declare anything [-fpermissive] make[2]: *** [CMakeFiles/aqemu.dir/Embedded_Display/vncview.o] Error 1 make[1]: *** [CMakeFiles/aqemu.dir/all] Error 2 make: *** [all] Error 2

For me, this returns a error in compiling: http://paste.archlinux-br.org/1888 Any suggestion ?

removed versioned dependencies

It's definitely not a problem of yaourt. It is a problem of the PKGBUILD. On Gentoo, where you have several versions of one package in the portage tree, the repo, such versioned dependencies are necessary, but not on Arch Linux, where you have only one version of a package in the repos. See the discussion in the comments for virtualbox-ext-oracle: http://aur.archlinux.org/packages.php?ID=44761&comments=all The problem is not yaourt, but pacman, because if a package needs a specific version of another package and the other package needs a specific version of the first package it's not possible to update the system with pacman -Syu resp. yaourt -Syua. If you have only packages from the binary repos installed it doesn't matter that much, because pacman -Syu first downloads the full package database and then checks for dependency issues. If you have versioned dependencies in there they are resolved at that time and pacman knows that the necessary packages are in the repos and will be updated at the same time. This is not possible with AUR packages. So yaourt or clyde can not do these checks. And if you have an AUR package installed which needs a specific version of a package from the repos (versioned dependency) then neither pacman nor yaourt can update the system, because pacman -Syu sees that the installed AUR package needs the installed version from the repo, but can't find the AUR package and can't check if there's a new version of it. So pacman -Syu will fail and the user can't update anything. And yaourt -Syua will fail for exactly the same reason. So, please, remove the versioned dependencies. You really can assume that everybody has an up-to-date system. If someone doesn't update his system regularly, doesn't have the latest version installed, and gets into trouble because of this it's his own problem. And that's common Arch Linux policy.

qemu as dependency is sufficient, as qemu-kvm provides qemu, yes. I was just wondering if dependencies can be linked with logical operators, too. If yaourt, etc. can't handle minimum/maximum version numbers I consider it to be a problem of yaourt, not of the PKGBUILD. It is mentioned in the wiki, and there are packages which have that data. Also, pacman can Ignore package upgrades if you want to stick with some version for your own particular reason, so I may NOT consider that the system has all the latest versions of its packages.

@schmoemi: It's sufficient to add qemu to depends. qemu-kvm has a provides=('qemu'). And you really should remove the version numbers in the depends array. This can lead to massive problems when updating the system with AUR wrappers like yaourt or clyde. And it's not common, because Arch Linux is a rolling release distro with only one version of a software package in the repos. So it can be assumed that everybody has the latest version of a package installed.

Does PKGBUILD know the OR operator?

In depends : qemu or qemu-kvm would be nice.

Done! :-)

@schmoemi: One other suggestion. You can or should remove the "|| return 1", because in the meantime those errors are caught and handled by makepkg itself. And you should set yourself as Maintainer instead of Contributor. ;-)