I'm going to add to my fork the latest version 12.1.0.3272444, currently there are older versions too, namely 12.0.0.2985596 and 12.0.1.3160714. The versioning of vmware-modules ebuild is currently done as X.Y where X is the version number in vmmon-only/include/iocontrols.h while Y is taken from the third component of vmware-workstation's version. With this scheme we'd have:
It's clear that the scheme above described doesn't work anymore if we want to have a different release for each workstation/player version, so that it's possible to have separate sets of patches (we know that upstream might release different sources with the same single version number).
I'd suggest to use the scheme X.Y.Z where Y.Z is taken from second and third components:
I'm going to add to my fork the latest version 12.1.0.3272444, currently there are older versions too, namely 12.0.0.2985596 and 12.0.1.3160714. The versioning of vmware-modules ebuild is currently done as X.Y where X is the version number in vmmon-only/include/iocontrols.h while Y is taken from the third component of vmware-workstation's version. With this scheme we'd have:
12.0.0.2985596 -> 308.0 12.0.1.3160714 -> 308.1 12.1.0.3272444 -> 308.0 (again)
It's clear that the scheme above described doesn't work anymore if we want to have a different release for each workstation/player version, so that it's possible to have separate sets of patches (we know that upstream might release different sources with the same single version number).
I'd suggest to use the scheme X.Y.Z where Y.Z is taken from second and third components:
12.0.0.2985596 -> 308.0.0 12.0.1.3160714 -> 308.0.1 12.1.0.3272444 -> 308.1.0
What do you think?