> > I can't see, how this can happen anyways. Anaconda just runs once (at > > installation), afterwards it can safely be removed (correct me, if I'm > > wrong). > > > > Could you please explain, why this should be useful for all our users? I > > think it's more sensible to install, when running on VMware. And also: > > why do you require this at all? > > > Rather than trying to only install it in particular scenarios, it is > better to install it everywhere and then make sure that it is a no-op > unless it is running inside VMWare. Not least because if we're building > a cloud image, the initial build environment likely won't involve VMware > at all, but the ultimate runtime environment may well be VMWare. I was thinking about this approach but the only downside is physical deployments and non-VMware VMs. I'm not sure if it is common to install unused packages on system. > The systemd unit file open-vm-tools includes already has a statement > ConditionVirtualization=vmware. Whether there is more work required > to make sure the package is a no-op on non-VMWare deployments is > something that'd need to be verified before inclusion in the core > package group. Yes, vmtoolsd service is a no-op in all non-VMware environments. In fact, it will simply exit even if systemd check is not there, because we do a platform check inside before starting the main loop. Thanks, Ravindra -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
