Hi!
Eventhough I understand your attitude towards beta releases for new
major releases which are unrealistic to support because of possible
drastic changes, would you be OK with the following idea to change you
stance of supporting vmware server v2 in the future?
First off, I understand that the massive amount of java etc applications
now included in VMware server v2 might cause quite some pain.
To make support for vmware server on Debian easier in general in the
future (and to aid system admins who don't want to install X on their
server), I'd suggest splitting vmware-package into 3 packages:
- vmware-package-common for kernel-module building,
- vmware-package-client (which depends vm..pkg-common and on the
various required X/GUI-related packages) for building clientside
applications like vmware-server-console, vmware-workstation and the
likes and
- vmware-package-server (which also depends on vm..pkg-common but not
the X/GUI-stuff for vmware-server (and hopefully - I'd be glad to help
out there - with support for vmware server v2 in the future, eventhough
EMC/vmware seems to have less and less interesting in continuing
developing this product considering their Virtual Infrastructure and ESX
offerings).
This does relate both to the current pain for people wanting to build
kernel modules and package vmware server where vmware-package depends on
X-related packages as well as future vmware server v2 support.
I hope this email wasn't too wrongfully adressed to this bugreport, but
I think they're strongly related anyways, so...
Last, but not least...
Would you be as kind as to provide more information on your current
situation leading to the conclusion that there never will be support for
vmware server v2?
Thanks!
--
Kind regards,
Benjamin Schallar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
