Adding open-vm-tools to core group
awilliam at redhat.com
Tue May 7 20:27:28 UTC 2013
On Tue, 2013-05-07 at 14:45 -0400, Bill Nottingham wrote:
> Ravindra Kumar (ravindrakumar at vmware.com) said:
> > > @core is supposed to be the minimum functional install. It is my
> > > understanding that, even under VMWare, open-vm-tools is not required for
> > > the system to be functional, so open-vm-tools does not belong in @core.
> > It is not required for system to be functional, but it also leaves
> > a significant gap in the VM to be fully operational unless Tools are
> > installed. I listed out a bunch of functionality that depends on
> > open-vm-tools in my other response.
> > If there are strong use cases that don't require that functionality
> > then probably it makes sense to not be part of core, otherwise, I think
> > it makes more sense to make open-vm-tools part of @core because sooner
> > or later users will end up installing these due to one or the other
> > use case.
> Perhaps a virt-agents group that contains open-vm-tools, hypervkvpd,
> qemu-guest-agent, etc?
Right, I was just thinking down those lines. Create such a group, and
have it installed by default. Makes sure the tools are available in most
cases, but not in minimal installs, and allows them to be easily added
or removed in any other config.
Only problem is it might need to be at least two groups, for an X/non-X
split. Right now, for instance, spice-vdagent is in the base-x group,
because all its functions are X-related, so there's no point having it
installed if you don't have X in the guest.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
More information about the devel