As of version 5.0.0.13124-r3, vmware does not use linux-mod. In fact, after recompiling the kernel, a full re-emerge of the package is not needed. Kernel modules are rebuilt with tool vmware-config.pl which can be call by ebuild <vmware ebuild> config. module-rebuild should handle this by properly calling vmware's ebuild config or by einfo-ing user has to run it on his own.
I understand vmware needs to be ported to linux-mod and that's not enough yet, the ebuild should be able to tell what it needs to done to rebuild its modules, namely ebuild `equery which =app-emulation/vmware-<installed-version>` config. what about extending module-rebuild database syntax from package --> emerge package to package --> emerge package package ebuild command --> ebuild <package's ebuild file> command package warning text --> print text as warning by module That should cover all possibilities.
What needs to happen is the ebuild needs to handle the modules. The problem is that vmware-config.pl does more than just compile modules, so I would have to duplicate the script into an ebuild, then remove the script from the vmware installation, to keep users from running it (and breaking the module-rebuild database)
Created attachment 79192 [details] Dirty Hack Ebuild for vmware kernel mods This is a dirty little ebuild I threw together. I basically lifted what was in the vmware-config.pl and implemented it in the ebuild. I add this ebuild to modules-rebuild. The only issue I have, is that I need to run a "module-rebuild populate" everytime before I build a new kernel and run module-rebuild. This probably isn't the proper way to do this but it works for me :) .
There's definitely another way of doing it, as other ebuilds for modules automatically register. At any rate, what I said before was *not* that it would be difficult to make the modules ebuild, but that I would need to duplicate the *other* functionality of vmware-config.pl into the vmware-workstation ebuild. A module ebuild is the easy part. I already have one. In fact, mine is for not only vmware-workstation, but also vmware-player, so that's not an issue, either.
This is one of those things which really depends on vmware sorting itself out and splitting out the kernel modules and the rest of the gubbins. bug #122500 is looking towards that, and once it is in portage it will automagically work. Resolving as CANTFIX for the time being.
This never really should have been closed.
Instead, it should have been reassigned. ;]
vertigo ~ # module-rebuild list | grep vmware =app-emulation/vmware-modules-1.0.0.13 This has been fixed with the introduction of the vmware-modules ebuilds to handle the modules.
