Bugzilla Bug 110027

Summary pretty much says it all...

Please search. :p

*** This bug has been marked as a duplicate of 109899 ***

...

Amazing, you assign a bug for yourself and it gets marked as a DUP by an
over-zealous bug-wrangler...

*** Bug 109899 has been marked as a duplicate of this bug. ***

Created an attachment (id=71133) [details]
preliminary ebuild

I have attached an ebuild that doesnt fail to install.	However the application
has not been tested to work.  Not sure if the startup scripts are going to be
valid.	Just copy the vmware-workstation dir to the vmware-player dir...

(In reply to comment #3)
> Amazing, you assign a bug for yourself and it gets marked as a DUP by an
> over-zealous bug-wrangler...

You are asked to look for existing bugs instead creating new ones as anyone
else. It was meant as a friendly short reminder.

Suggest that, as it appears there are some shared files and paths,
vmware-player
and vmware-workstation should block each other.

That is, unless someone comes up with a good reason why you'd want both - then
we'd need a third app (vmware-services ?) that handles the shared stuff.

<[Bug 109899]>
------- Additional Comment #1 From  Paul Kronenwetter  2005-10-20 07:17 PDT
[reply] -------

Just FYI - VMware Player comes with Workstation v5.5...
</[Bug 109899]>

I haven't tampered with the 5.5, but if the quoted comment is true a block would
be adequate in the future. It would also be lesser evel if proven to be false
measure.  

A good reason for both is if you have VMWare installed for your own virtual
machines, yet you also need to use the player to connect to machines on a
different computer.

Created an attachment (id=73720) [details]
VMware player ebuild

Here is an updated ebuild for vmware-player-1.0.0.18007 (adapted from the
vmware-workstation-5.5.0.18007-r1 ebuild and the vmware-player-1.0.0.16981
ebuild attached to this bug).

I have added a block on vmware-workstation. Tested and works for me.

For completeness, some files from the vmware-workstation files/ dir needs to 
be copied over for vmware-player: 90vmware, the config patch, vmware.rc and 
vmware.xml. The config patch needs to be renamed to 
vmware-player-1.0.0.18007-config.patch and the paths in 90vmware need to 
change to /opt/vmware/... instead of /opt/vmware/workstation/... 

(In reply to comment #11)
> For completeness, some files from the vmware-workstation files/ dir needs to 
> be copied over for vmware-player: 90vmware, the config patch, vmware.rc and 
> vmware.xml. The config patch needs to be renamed to 
> vmware-player-1.0.0.18007-config.patch and the paths in 90vmware need to 
> change to /opt/vmware/... instead of /opt/vmware/workstation/... 

Not exactly.  See, this needs to be modifed to install into /opt/vmware/player
and defainitely should *not* block vmware-workstation.  I'll be taking a closer
look at this during this week and try to get it into portage.

As much as I hate this, it wasn't a trivial task to make vmware-player and
vmware-workstation install side-by-side.  For one, the modules aren't compatible
across all versions of vmware-workstation, meaning we would only be able to have
shared services between specific branches.  In the end, a blocker really is the
only way to do this without spending significant resources.