@jhem thank you that worked!
Search Criteria
Package Details: vmware-workstation 17.6.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/vmware-workstation.git (read-only, click to copy) |
---|---|
Package Base: | vmware-workstation |
Description: | The industry standard for running multiple operating systems as virtual machines on a single Linux PC. |
Upstream URL: | https://www.vmware.com/products/workstation-for-linux.html |
Keywords: | dkms ovftool player vmplayer vmware workstation |
Licenses: | custom |
Conflicts: | vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services |
Provides: | vmware-ovftool |
Submitter: | synthead |
Maintainer: | jihem |
Last Packager: | jihem |
Votes: | 204 |
Popularity: | 4.09 |
First Submitted: | 2017-02-10 19:04 (UTC) |
Last Updated: | 2024-10-11 05:17 (UTC) |
Dependencies (13)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- fuse2
- gcr
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- gtkmm3
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libaio (libaio-gitAUR)
- libcanberra
- libxcrypt-compat
- pcsclite (pcsclite-gitAUR)
- vmware-keymapsAUR
- sqlite (sqlite-fossilAUR) (make)
- linux-headers (optional) – build modules against Arch kernel
Required by (6)
Sources (22)
- config
- configure-initscript.sh
- dkms.conf.in
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linux-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-netware-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/core/VMware-Workstation-17.6.1-24319023.x86_64.bundle.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/packages/vmware-tools-windows-12.4.5-23787635.x86_64.component.tar
- Makefile
- vmmon.patch
- vmnet.patch
- vmware-bootstrap
- vmware-environment.sh
- vmware-networks-configuration.service
- vmware-networks.path
- vmware-networks.service
- vmware-usbarbitrator.path
- vmware-usbarbitrator.service
- vmware-vix-bootstrap
Latest Comments
« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 66 Next › Last »
zangoku commented on 2019-03-18 01:15 (UTC)
jihem commented on 2019-03-17 08:24 (UTC) (edited on 2019-03-17 08:25 (UTC) by jihem)
zangoku: try to add a backslash before the character *
zangoku commented on 2019-03-17 07:25 (UTC)
@jhem, I must use the slash or else I get:
zsh: no matches found: usr/lib/vmware/xkeymap/*
jihem commented on 2019-03-16 10:00 (UTC)
zangoku: just remove the first slash on the keymap filenames.
GiRa: Since I am the maintainer of this package, I had some complaints of people who use vmware-workstation and vmware-horizon-client packages because these packages have common files and on each update, they need to use --force/--overwrite option to install the updated package. With the vmware-horizon-client maintainer and vmware-keymaps author, we had a discussion by mail and the better solution we found is to put the common files in a new package.
I understand your point of view but I don't want to come back to this decision. But, just to reassure you, these keymap files haven't been changed since at least VMware Workstation 11, so this package should be updated rarely or never. Also, you could suggest to vmware-keymaps maintainer to change the PKGBUILD to extract keymap files from an official VMware bundle, instead of taking them from a private repository.
GiRa commented on 2019-03-15 14:05 (UTC) (edited on 2019-03-15 14:07 (UTC) by GiRa)
I may say that adding an external repository for they keymaps makes updating more complex.
I always review what changed at each new release of an AUR package. Basically it's a full code review at the first installation and then incremental ones which usually take less than a minute.
Having an external, non-official, third-party repo makes the updates more complex. A conscious user is forced to clone the external repo manually and review it at every update.
Was it a big amount of work to maintain the keymaps? You already do a lot, so I am not pretending to change your ways. I simply want to understand :)
EDIT: I see in the gitlog that this is needed for compatibility with vmware-horizon. Is there any other feasible alternative?
zangoku commented on 2019-03-14 21:47 (UTC)
@jhem
I am getting these errors when trying to install keymaps:
error: could not open file /usr/lib/vmware/xkeymap/be104: Unrecognized archive format error: '/usr/lib/vmware/xkeymap/be104': cannot open package file
jihem commented on 2019-03-13 10:50 (UTC)
zangoku: build the package vmware-keymaps as usual, but without the -i option of makepkg. Then, install it with the following line:
pacman -U --asdeps --overwrite usr/lib/vmware/xkeymap/* vmware-keymaps-1.0-1-any.pkg.tar.xz
Then, update vmware-workstation.
mpei commented on 2019-03-13 03:41 (UTC)
@jihem: I just tried again at current state of arch, loaded the kernel modules and it works perfectly. Thank you!
zangoku commented on 2019-03-13 02:39 (UTC)
How can I use the overwrite option when install a package from the AUR ? I usually use git clone then makepkg.
Pinned Comments
jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)
After the first installation, please:
1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...
2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)
3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :
vmware-networks: to have network access inside VMs
vmware-usbarbitrator: to connect USB devices inside VMs