Arch Linux User Repository

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

@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.

Is there a specific reason I have to uninstall this package to update my system? I'm no expert, but that is very annoying. If there is a good reason then so be it, but I'd love to know what it is. Thanks!

And why in the world does this have a versioned dependency again? Please get rid of that. It does not make any sense and is _wrong_, unless someone shows us why. Arch is rolling-release and there is only one version of a package at a time. We use versioned dependencies for people upgrading from CD installations that may be older than supported.

I endorse what @cyberpatrol says, and I think that a solution shall to be found, because the current behaviour of this package is annoying. But I don't think that this is a versioning problem, because of my case is that I have virtualbox_bin, and not virtualbox, and there is a conflict. A fast check at https://wiki.archlinux.org/index.php/Virtualbox suggest that we have to use virtualbox in community, and if you want extras we have to install this package. Am I right?, because I am not sure of this. If i is true, it is necessary to INFORM users what they have to do, because the normal procedure of pacman is broken. And this is not because users do not know what to do, but to save time.

I do comprehend the most obvious. I have explained it.