app-emulation/vmware-workstation & app-emulation/vmware-workstation-tools (?) need bumps. Release notes here: http://www.vmware.com/support/ws55/doc/releasenotes_ws55.html
I've been working on them. The thing is that new versions require more work than bumps, because the vmware-any-any-update releases no longer work on them.
bug #144685 is a duplicate of this bug
Any date, or ebuilds for testing, for the new release? I need new support of - Solaris x86 10, 10 Update 1, 32-bit, 64-bit now present in WS 5.5.2
*** Bug 144685 has been marked as a duplicate of this bug. ***
*** Bug 145785 has been marked as a duplicate of this bug. ***
The new versions of vmware-player and vmware-workstation do not use the module sources from vmware-any-any-update104, but need to use their own internal modules. This is actually why the ebuilds have not been bumped yet. They require much greater changes than just the contents of a few variables. I should be working on these ebuilds some more over the upcoming week, but work has me rather busy at this time.
*** Bug 146809 has been marked as a duplicate of this bug. ***
*** Bug 146832 has been marked as a duplicate of this bug. ***
Created attachment 97297 [details] minimally modded vmware workstation ebuild I got vmware workstation 5.5.2 up and running using this ebuild and a modified version of 002_all_pagebreak-detection-fix.patch. this probably isn't the correct set of changes - but it worked for me ...
Created attachment 97298 [details] updated all_pagebreak-detection-fix for ebuild in comment#9 this is the updated patch referred to in comment#9
The new vmware-workstation requires vmware-modules 1.0.0.15?
It wouldn't surprise me. The codebase for the modules tends to be shared, and when one bumps the version number, all the next versions come out requiring that one. It's just a pity the vmware-any-any builds don't keep up with the main versions... We should try and get special dispensation from vmware to repackage the modules stand alone, so that people don't have to keep dragging in a huge (and potentially unnecessary) shared package just for the modules. As long as the internal version number (which I think currently stands at 138) is the met, it should all work fine...
Yeah. Having to download 100+MB of VMware Server to get Workstation working definitely sucks.
I have added this to portage, but it is still masked currently. The *only* reason it is masked is because it is using vmware-modules-1.0.0.15, which downloads vmware server (100MB+) and I haven't thought up a better solution yet.