Could someone just bump the current vmware-workstation-tools-5.5.3.ebuild to vmware-workstation-tools-6.0.2.ebuild it works very nicely. The 6.0.2 tar ball name is VMwareTools-6.0.2-59824.tar.gz Reproducible: Always Steps to Reproduce:
Yannick, we're phasing out the vmware-workstation-tools packages in favour of the open-vm-tools package which is opensource and tends to get updated more frequently that the vmware tools packages. It's available in the tree, and should work for all versions of vmware. Should you have any problems with open-vm-tools, or notice a version bump available for that package, please file new bugs and we'll look into them... 5:)
Anyway to simply bump the revision in the portage tree so that I don't get mine downgraded. Low cost no? I am all for open-source yet I feel having the possibility to still use vmware tools is a good thing as well.
and... open-vm-tools are masked.
Yannick, The open-vm-tools, which are officially developed by vmware staff, were designed to avoid situations such as new kernel releases where the pre-packaged tools break, or security issues in the tools that can't be quickly corrected and would otherwise require a version bump in the hosting package. Effectively, they are the latest versions of vmware-workstation-tools, they come from the same codebase. Since the open-vm-tools package is official, fully interoperable with all vmware products (as far as our testers have shown) and allows us to push out fixes for new kernels more easily, we will not be adding any new versions of vmware-*-tools to the portage tree, and we are recommending all users upgrade to open-vm-tools. Changing from one package to another is not a particularly high cost, and we'll be investigating a pkgmove to make that transition automatic in the future. Open-vm-tools is marked ~ARCH, much like vmware-workstation-6, so there's little reason to need the tools stable if they're being run on a testing package. If you'd like to have either package stabilized, please file a stabilization bug against that package.
*** Bug 213089 has been marked as a duplicate of this bug. ***
