Arch Linux User Repository

There is no version dependency on this package on purpose! You could read comments back from 2011 to understand why.

No, please, not again a versioned dependency! This just causes big trouble with updating the system like discussed very often. @monson: Arch Linux is a rolling release distro which has only one (the newest) version of each package in the repos. So it can be assumed that everybody has the newest version installed. Keep your system up-to-date and regularly run `pacman -Syu` or even better `yaourt -Syua` and you won't have any problems with that. With versioned dependencies you regularly need to manually uninstall this package to be able to run a `pacman -Syu` and manuall reinstall it afterwards.

To be convenient to most people, I think it's better to modify to depends=("virtualbox=$pkgver"), as the "virtualbox_bin" PKGBUILD already provides=("virtualbox=${pkgver}").

qs9rx: Now virtualbox_bin is already in repo. Just try to update virtualbox_bin first, and this package hereafter, it should work. However I'm sure seblu will fix it soon.

yes it did not check. You can find why in previous comment.

Proceed with installation? [Y/n] (1/1) checking package integrity [#########################################################] 100% (1/1) checking for file conflicts [#########################################################] 100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% (1/1) upgrading virtualbox-ext-oracle [#########################################################] 100% 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack-4.1.0.vbox-extpack": VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=00000000 ErrInfo='VirtualBox version mismatch - expected 4.1 got 4.0' error: command failed to execute correctly --------------------------------------------- pacman -Qs gives me local/virtualbox 4.0.12-1 local/virtualbox-additions 4.0.12-1 local/virtualbox-ext-oracle 4.1.0-1 So I guess it did not check for the needed vbox version which is not in the repositories yet (just released today).

By the way, what cyberpatrol said about all the files in "$startdir" automatically being symlinked into "$srcdir" was not entirely accurate. Only the ones listed in the source=() section are (thus passing the integrity check first).

We are on the same wavelength. I was not sure about deprecation (will be removed) of startdir even though I had no doubt of the fact that it was necessary to use ${src/pkg}dir. it may seem paradoxical but not. I proposed a patch on pacman-dev, to update man page of PKGBUILD.

I'm not quite picking up what you're saying but what I _think_ you mean is that you checked the pacman/makepkg source code and there was a cd command to 'src', am I right? You also said that "$startdir" was being used there (even though it's otherwise deprecated), which would makes this all really simple and easy, since: "$startdir/src" = "$srcdir" (and "$startdir/pkg" = "$pkgdir"). But again, if you meant something else then please do enlighten me.