On Tue, 2013-05-07 at 14:45 -0700, Ravindra Kumar wrote: > >> 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. > > I think I can do this, but this means I will have to include the new > group in all the other configs? Will I be allowed to make that change > in comps file? > > 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. > > This is not an issue for open-vm-tools. open-vm-tools X components are > already packaged separately as open-vm-tools-desktop. My plan was to > include open-vm-tools-desktop in a common desktop config like gnome and kde. Well, no, that means it precisely *is* an issue :) that adds open-vm-tools to the list of reasons we might want to have two virt-agents groups, call them virt-agents and virt-agents-x or something. You'd want open-vm-tools to be in one and open-vm-tools-x to be in the other. What we do with the groups is another question; there are various options. We could just put the 'virt-agents' group in the 'standard' group and the 'virt-agents-x' group in the 'base-x' group, for instance. Or we could add them directly to other groups. Bill's the expert here, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
