Patch to follow
Created attachment 75021 [details, diff] vmware-console modular X dependencies
Any ebuild changes will be performed in new package.
Matt, please either commit an -r1 (needlessly, imho) or get this committed asap. It's not user-visible, so I don't think it should be a new revision. Thanks, Donnie
The new ESX ebuild has the modular x changes recommended.
Right, from discussions in bug 119330 and bug 56881, it appears that the gsx related ebuilds aren't really wanted by anyone, especially since vmware-server just got released for free. I've been writing some ebuilds for the new vmware-server packages, however, we still have the old gsx ebuilds which, now that the esx-console packages have their own ebuild, should probably be cropped down to just the 3.x numbers and have the modular X dependencies made for them. Please also note that the vmware-server-console currently does not interact with GSX server, and thus the gsx-console ebuilds cannot be completely removed yet. So since the patch is already here and isn't a user visible change, could *someone* please commit these soon (after checking them, of course)? That way we can close this bug and get closer to a modular X release. Thanks very much...
(In reply to comment #5) > Right, from discussions in bug 119330 and bug 56881, it appears that the gsx > related ebuilds aren't really wanted by anyone, especially since vmware-server > just got released for free. For now... VMWare has never said that it will remain free. It is simply free now while it is in beta. Of course, they have not said that it won't be free, either. My main point here is that we cannot rely on the fact that VMWare Server will remain free, plus we need to rertain support for people who have not yet upgraded.
Chris, sorry, I can see how you took that comment the wrong way. When I said it appeared they weren't wanted, what I meant was, it appeared that no one in the Gentoo vmware team wanted to support or maintain them. I mentioned that vmware-server's console is not compatible with gsx server, so we *must* maintain the gsx-console ebuilds, which is why I'm advocating getting them updated to modular X dependencies. The reason I posted is that I was informed in other bugs that the gsx ebuild would get the modular X treatment perhaps a day after the esx ebuild did. Unfortunately the esx ebuild was fixed a while ago, whilst the gsx ebuild hasn't been touched. I was hoping that someone could help fix this problem, for which I supplied a patch two months ago, and that if the vmware team were a little too busy to fix it (since they have yet to fix the even older gsx bug of 98060), perhaps someone else could make this non-user-visible change, so that modular X can progress and eventually be unmasked? I look forward to seeing a fixed version of this ebuild finally hit portage. Thanks...
> For now... VMWare has never said that it will remain free. It is simply free > now while it is in beta. Of course, they have not said that it won't be free, > either. My main point here is that we cannot rely on the fact that VMWare > Server will remain free, plus we need to rertain support for people who have > not yet upgraded. > VMWare sent out an email to all GSX license holders last week notifying them that: a) vmware server was the replacement for gsx b) they really should migrate over c) they would provide contractually obligated support for current gsx software versions for 2 years. I got the feeling from reading it that they otherwise didnt want to hear about GSX ever again. They were just doing what was required of them for current license holders. So, unless stability is criticality, gsx users really should migrate over to vmware server. I dont see much point in our investing resources in gsx maintenance going forward. I dont remember whether the price of vmware server was discussed, but i got the impression that it was a free upgrade for all gsx users. Furthermore, all the press reports, etc, I've seen indicate that vmware wants to keep the server pricing as close to zero as possible and make their profit off ESX and enterprise management software.
> > I mentioned that vmware-server's console is not compatible with gsx server, so > we *must* maintain the gsx-console ebuilds, which is why I'm advocating getting > them updated to modular X dependencies. The reason I posted is that I was > informed in other bugs that the gsx ebuild would get the modular X treatment > perhaps a day after the esx ebuild did. Unfortunately the esx ebuild was fixed > a while ago, whilst the gsx ebuild hasn't been touched. > Yes, this was my bad. I have access to GSX server, but it is painful to get to that box. I also realized that I hadnt updated the gsx box in forever, so apparently other people were interested in newer versions of the console/etc than what I was using. I'll go ahead and write the new ebuild today and commit it. That should close off this issue. Note that given what is going on with the vmware-server stuff, I dont want to provide support long term for gsx here - my box will probably switch over to ESX which is what I was trying to hint at in a prior messege.
That'd be great Matthew, thanks. I don't blame you for not wanting to spend much more time on GSX (or even server), but since it's (currently) free, it's much easier for me to test (I can even run it at home!) and develop ebuilds for, so I may be able to ease some of the pressure. 5:) Thanks again for the great work you guys are doing! Keep it up...
gsx console ebuild commited under 'vmware-gsx-console'. The only thing left to do is to deprecate/delete the old 'vmware-console' package as it should no longer be used. I'm not sure what/if anything I should do for that..... I'm hesitant to just do a cvs rm :)
(In reply to comment #6) > (In reply to comment #5) > > Right, from discussions in bug 119330 and bug 56881, it appears that the gsx > > related ebuilds aren't really wanted by anyone, especially since vmware-server > > just got released for free. > > For now... VMWare has never said that it will remain free. It is simply free > now while it is in beta. Of course, they have not said that it won't be free, > either. My main point here is that we cannot rely on the fact that VMWare > Server will remain free, plus we need to rertain support for people who have > not yet upgraded. I generally don't like using blogs for facts, but this is from VMWare employees: http://www.chipx86.com/blog/?p=153 What VMware Server Is: * Free virtualization for servers. * A way to give people free virtualization with the hope that they
(In reply to comment #6) > (In reply to comment #5) > > Right, from discussions in bug 119330 and bug 56881, it appears that the gsx > > related ebuilds aren't really wanted by anyone, especially since vmware-server > > just got released for free. > > For now... VMWare has never said that it will remain free. It is simply free > now while it is in beta. Of course, they have not said that it won't be free, > either. My main point here is that we cannot rely on the fact that VMWare > Server will remain free, plus we need to rertain support for people who have > not yet upgraded. I generally don't like using blogs for facts, but this is from VMWare employees: http://www.chipx86.com/blog/?p=153 What VMware Server Is: * Free virtualization for servers. * A way to give people free virtualization with the hope that theyll consider eventually moving up to ESX for the enterprise. Or you could go straight to the source: http://www.vmware.com/products/gsx/ "VMware Servera free virtualization product for Windows and Linux servers .... The free VMware Server represents the upgrade path for all GSX Server customers."
This bug should have been closed awhile ago. I'm not aware of any modular x issues outstanding.
