Arch Linux User Repository

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

@seblu: Did you test it with pacman -Syu when virtualbox in [community] was updated, too? Just updating virtualbox-ext-oracle with yaourt could bring wrong results, which don't help with this issue. This issue has to do with circular dependencies. Btw., it's long ago that virtualbox was updated from 3 to 4 and this update is/was done by pacman -Syu, too. So there's definitely no need anymore for this versioned dependency. It was infact not needed before to get a correct transition from 3 to 4, just because of the rolling release and because there's only one version of a package in the repos. It can be expected from Arch users to update their systems regularly and not only update one single package from AUR. So it's definitely the best to remove these versioned dependency, and it's btw. Arch plolicy. Believe me.

so, i make a test with a fake 4.0.3 version of virtualbox... rwolf ~/scm/archrep/virtualbox_bin $ yaourt -U virtualbox_bin-4.0.3-1-x86_64.pkg.tar.xz resolving dependencies... looking for inter-conflicts... Targets (1): virtualbox_bin-4.0.3-1 Total Download Size: 0,00 MB Total Installed Size: 129,80 MB Proceed with installation? [Y/n] checking package integrity... (1/1) checking for file conflicts [########################################################################################] 100% (1/1) upgrading virtualbox_bin [########################################################################################] 100% :: Unloading VirtualBox kernel modules [BUSY] [DONE] :: Recompiling VirtualBox kernel modules [BUSY] [DONE] :: Reloading VirtualBox kernel modules [BUSY] [DONE]

ok i will test

@seblu:>= does not work. Thats the line I changed to be able to update.

@cyberpatrol: firstly i make this version condition to avoid users from 3.x to setup this extentions before update in virtualbox 4.0, because install script needs a virtualbox version >= 4 ! So a good versioning is at least >=4 not without any version condition. Regarding release rolling schema, you're right, we have only one version at the same time in repository. But we also have to manage correclty transition between our version. Your initial request was about that. So, have one package at a time, is not synonymous with "forget everything about the past". Why do you want to change this dependency? It's free and without pain and escape someone with version 3.x to mistaken using this package? I think it's wiser to keep it for now. About >=, i hope to not be false. In next virtualbox update, pacman allow setup of this new version, because there is no conflict. virtualbox-ext-oracle need a version more recent than itself. Same things for this package update. Time is a chatterbox who speak without being questioned. W&S

@seblu: Sorry, I must have missed this change, but I don't think that >= works, because the previous installed version is <=. So >= has at least theoretically the same effect than =. Why don't you just remove this? Arch Linux is a rolling release distro with only one version of a package in the repos. I repeat myself.

@cyberpatrol: As you can see, the first time you speek about this dependency issue, i updated the package and changing = to >=. Reading later comments, this decision seems to be fair and take in consideration the both point of view. This is why i left >=. So what's wrong with >=? On new version of virtualbox package, you will be able to update virtualbox without removing previous virtualbox-ext-oracle. On new version of virtualbox-ext-oracle, you need to have new virtualbox version setup before (what we want).

@seblu: The versioned dependency: depends=("virtualbox>=$pkgver") => depends=("virtualbox")

@mektub: Which changement? What's wrong?

I had to change PKGBUILD to be able to update my system. I don't know if I did it the right way. Someone more knowledgeable should take a look at it, something is wrong with the packaging of virtualbox-ext-oracle.