+++ This bug was initially created as a clone of Bug #119329 +++ This is the tracking ticket for the GSX version of the vmware-console package.
GSX console package needs to be created before we bump up any more versions.
Has there been any further news on this since it's blocking both a 4 month old "new" version of vmware-console and the modular X dependencies which are due for release in the next couple of days? Any information on how these are progressing would be helpful. Thanks...
(In reply to comment #2) > Has there been any further news on this since it's blocking both a 4 month old > "new" version of vmware-console and the modular X dependencies which are due > for release in the next couple of days? Any information on how these are > progressing would be helpful. Thanks... > The new vmware-esx and vmware-gsx versions of vmware-console will be available in the next few days (worst case would be over the weekend). Shortly thereafter, the old package will be deprecated and slated for removal. I am not sure if move-package applies here since their two are two quite viable descendents.
Doesn't the current version in the tree really only work for GSX? I would think doing a package move to vmware-console-gsx (only if that is truly the case) would be the best move. Again, that is only if the current version only really works on GSX.
(In reply to comment #4) > Doesn't the current version in the tree really only work for GSX? I would > think doing a package move to vmware-console-gsx (only if that is truly the > case) would be the best move. Again, that is only if the current version only > really works on GSX. > I suspect the original package maintainer emphasized the GSX packages, but what we have installed is really a mismash of different ebuild versions designed for different platforms. The 2.x ebuilds are for ESX and the 3.X are for GSX. That does not mean the GSX versions are necessarily newer and do everything the ESX packages do. The 3.x packages were only designed for GSX, although they can be used in a limited fashion with ESX. I'm sure when the 3.x version of ESX comes out, there will be a 3.x version of the console tools software that should be only used with ESX and not GSX. Therefore, I am not sure that a package move is really appropriate here. Note that I test on ESX much more frequently than GSX, so my GSX updates are going to be slower. I'll try to get the ESX ebuild committed tommorow, and the GSX the day after. I havent even looked at the modular X changes yet.
Unfotunately, modular X dependencies are a requirement for anything new going into the tree. If you need assistance with this, please let me know. For binary packages, it is actually quite easy.
Also, please see bug 115955 for an example of how to convert the 3.1.0.9089 ebuild to have modular X dependencies. Hope this helps...
If it would be of any use, I have two GSX servers I can connect to, so I'd be happy to test out any ebuilds before they go directly into the tree. I'm not certain where to find them though. If you'd be able to post them to your dev area, or attach them here, I'd be happy to give them a test run for you, and fix the modular-x dependencies too...
I looked into modifying the ebuild mentioned in bug 98060 to have modular x dependencies and fit in with the vmware-gsx-console naming scheme. The problem is that recently vmware ebuilds have been installing to /opt/vmware/workstation or /opt/vmware/<packagename>, which seems like a great idea, but means a decision has to be made about the esx/gsx naming convention. Since vmware-esx-console just went into the tree, I checked where it installed to and found out it installed directly into /opt/vmware/! I don't know whether this is correct, and if it's not, should I be installing into /opt/vmware/console or /opt/vmware/gsx-console/ or /opt/vmware/console/gsx? Also with the announcement of VmwareServer (which will be free, see http://www.theregister.co.uk/2006/02/03/vmware_goes_free/), is there going to be yet another console package to get an ebuild out for? If anyone can offer help for getting a vmware-gsx-console ebuild out, it would be most appreciated, and I'd be happy to carry out any testing anyone may want...
Created attachment 79120 [details] vmware-server-console-1.0.0.20925.ebuild Ok, so this is an ebuild for the newly released vmware-server's console package. The paths are I agree beginning to get a bit unweildy, but at least everything is kept in an easily found directory structure. Apparently this can't be installed on a machine running any other vmware software, although that's unverified. I have however tried using an old console to hook up to a new server (which fails with an error message) and using this console to hook up to an old server (which hangs the console without any message). And finally, there are a few niceties that I haven't included but which would be nice to see, namely symlinks for vmware-console etc. in /usr/bin, and patching the console/installer to use /etc/vmware/server/console rather than /etc/vmware-console. However, it works, and hopefully people can test it a bit before it goes into portage. Thanks...
Created attachment 79121 [details] Associated 99vmware-console file This is just for the ebuild I just posted.
Doh, I just noticed that I rather unhelpfully forgot the modular X dependencies in that ebuild, I'll try and clean it up sometime when I get the chance, but that would need changing before it gets commited to the portage tree...
DOH! Well, I discovered that xinetd is now set with sensible defaults, to only allow access from localhost. No wonder the client was timing out. That seems to have fixed it, so it's quite possible that that ebuild may do a valid install (once you edit /etc/xinetd.conf). Lemme know if you get good results/bad results/weird results and I'll keep trying to fix it up until it's ready for use...
Wrong bug, sorry! Sorry about this spam too. Not a good day. 5:(
package commited.
I have version 3.2.1-19281 running on both EM64T and AMD64 and seems to be working ok. Only bug is, that if the destination doesn't actually respond as a GSX server, it hangs. If the GSX server actually exists and replies it seems to work ok so far. Let me know if you need more information. My first bug entry. I have a couple GSX servers I can test with if needed.
