The openvz-sources ebuilds are assigned a version based on the upstream openvz patch. However, the upstream openvz patch version is "reset" for every new kernel release. For example, the following openvz versions can happen in chronological order: 028.027 (for kernel 2.6.18) 003.000 (for kernel 2.6.23) This results in openvz-sources not having chronological version numbers. Solution: Append the OpenVZ version number to the kernel version number. So the above chronological releases would become: 2.6.18.028.027 (ie. openvz-sources-2.6.18.028.027.ebuild) 2.6.23.003.000 (ie. openvz-sources-2.6.23.003.000.ebuild) In my opinion, this is easier to understand and will allow Portage to properly compare the version of openvz-sources ebuilds when they span more than one kernel version. Reproducible: Always
(In reply to comment #0) > In my opinion, this is easier to understand and will allow Portage to properly > compare the version of openvz-sources ebuilds as long as upstream keeps this versioning, which will probably not happen... nevertheless, have fun updating these, i'm sick of it..
Ok. Plan is to do this with the next bump, then stabilize that kernel and clean old with wrong versions.
Starting with 2.6.18.028.049 versioning changed. Fixed.
Cool! :) Thanks for doing this.
