Arch Linux User Repository

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

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.

@det: i test this when i've done my first package, but before your suggestion i never take time to read makepkg source how it was done and if my conclusions was correct. Proof against the experience...

And a simple 'pwd' in the beginning of a(ny) function is a simple way to find out the default build directory (even package() functions are executed from "$srcdir").

ok thx.

$startdir is deprecated. In case of doubt the wiki and every developer who has said that several times on the mailing lists are right. And, btw., every file in $startdir is symlinked to $srcdir. So there's no need to use $startdir, no matter if it's deprecated or not.

I will clean this in next release. About deprecation of startdir, this is not written in man page of PKGBUILD, but it's written on the wiki (who is right?). In source code, startdir is used, so i don't think it's deprecated! But here, I agree it's unnecessary. About build()/package()/whatever() functions, i don't find any informations in manual or wiki about where it should when function is run. In source code, there is a cd in src before every function call. Thanks for the suggestions!