misc: discontinue Player related versions and tags

For quite long, VMware Workstation and Player have been distributed with
identical host module source. Therefore it seems unnecessary to maintain
two sets of branches and tags and 17.0.0 release is a nice opportunity to
discontinue "player-*" branches and "p*" tags. To reduce the mess, those
will be preserved and created for pre-17 products but no new Player related
branches and tags will be created for versions 17.x and newer unless the
module sources diverge in the future.

Update the README and INSTALL files to reflect this change and replace
14.1.1 version with 17.0.0 in examples.
This commit is contained in:
Michal Kubecek 2022-11-18 13:01:45 +01:00
parent 342ff44e75
commit 8dd494fa17
2 changed files with 35 additions and 24 deletions

46
INSTALL
View File

@ -4,27 +4,33 @@ either build the modules from source and install them ourselves or replace
VMware provided source tarballs with patched ones and let it use its own
vmware-modconfig tool.
In the text below, VMWare Workstation/Player 17.0.0 is used as an example.
Replace the occurences of "17.0.0" with your product version. For versions
before 17.0.0, there are also "player-*" branches and "p*" tags for VMware
Player but as the module source is identical between Workstation and Player
of the same version, one can use either.
0. Quick guide for impatient
----------------------------
First method (build and install):
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-14.1.1.tar.gz
tar -xzf workstation-14.1.1.tar.gz
cd vmware-host-modules-workstation-14.1.1
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.0.0.tar.gz
tar -xzf workstation-17.0.0.tar.gz
cd vmware-host-modules-workstation-17.0.0
make
make install
Last command must be executed with root privileges (first four shouldn't).
Based on your VMware product, replace "14.1.1" with your installed version
and/or "workstation" with "player".
Based on your VMware product, replace "17.0.0" with your installed version.
Second method (replace original tarballs):
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-14.1.1.tar.gz
tar -xzf workstation-14.1.1.tar.gz
cd vmware-host-modules-workstation-14.1.1
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.0.0.tar.gz
tar -xzf workstation-17.0.0.tar.gz
cd vmware-host-modules-workstation-17.0.0
tar -cf vmmon.tar vmmon-only
tar -cf vmnet.tar vmnet-only
cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/
@ -55,14 +61,14 @@ Branch "master" cannot be used to build modules, it contains only common
files so that changes in them can be merged into all other branches easily.
To get actual sources, checkout a "real" branch, e.g.
git checkout workstation-14.1.1
git checkout workstation-17.0.0
Branch name consists of "workstation" (for Workstation) or "player" (for
Player), a dash and version number ("14.1.1" here). Always use correct
product and version, the modules check if internal source version matches
installed product and refuse to load otherwise. Actually, in all recent
versions, "workstation" and "player" sources have been identical but there
is no guarantee it will always be the case.
Branch name consists of "workstation" followed with a dash and version
number ("17.0.0" here). Always use correct product version, the modules
check if internal source version matches installed product and refuse to
load otherwise. When unsure, the version of currently installed Workstation
or Player can be found in /etc/vmware/config on line starting with
"product.version".
To pull out updated branch (if there are new commits), run "git pull", to
switch to a new branch run "git fetch" and "git checkout ...".
@ -74,9 +80,9 @@ switch to a new branch run "git fetch" and "git checkout ...".
GitHub allows to download a particular snapshot (branch or tag) directly
without git:
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-14.1.1.tar.gz
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.0.0.tar.gz
where "workstation" and "14.1.1" have the same meaning as in section 1a.
where "workstation" and "17.0.0" have the same meaning as in section 1a.
Any other tool can be used to retrieve the URL, of course. It's also
possible to download directly from the web interface, switch to the branch
you are interested in, click the "Clone or download" button and then
@ -84,11 +90,11 @@ you are interested in, click the "Clone or download" button and then
Unpack the downloaded archive
tar -xzf workstation-14.1.1.tar.gz
tar -xzf workstation-17.0.0.tar.gz
or
unzip vmware-host-modules-workstation-14.1.1.zip
unzip vmware-host-modules-workstation-17.0.0.zip
depending on archive type. Then change to the resulting directory.
@ -113,7 +119,7 @@ directory with kernel modules (under normal circumstances, this should be
only root). The VM_UNAME variable can be used to install for a different
kernel. Unless you know well what are you doing and why, the same value
should be always used for "make" and "make install". That's why makefile
checks if vermagic tag of the moudules match VM_UNAME (or current kernel if
checks if vermagic tag of the modules match VM_UNAME (or current kernel if
VM_UNAME isn't set).
If DESTDIR is not set (or is empty), "make install" also runs depmod to

13
README
View File

@ -10,10 +10,15 @@ respectively. Tags of the form "p${version}" (e.g. "p12.5.5") and
"w${version}" correspond to clean unpacked sources of modules from
a particular version of Player or Workstation.
From these tags, branches "player-${version}" and "workstation-${version}"
are forked. These branches track changes needed to build these modules
against recent kernel versions. In general, one should always use current
branch head for the build.
From these tags, branches "workstation-${version}" is forked. This branch
tracks changes needed to build the modules against recent kernel versions.
In general, one should always use current branch head for the build. For
versions before 17.0, there are also branches "player-${version}" but as
the module sources have been identical between Workstation and Player for
quite long, there seems to be no need to duplicate the work. Therefore the
"workstation-*" branches should be also used for Player >= 17.0 (and can be
in fact used for older as well). If the situation changes in the future,
Player related branches can be introduced again.
In the past, tags in the form "w${ver}-k${ver}" and "p${ver}-k${kver}" were
also provided to mark the snapshots deemed sufficient to build modules for