Adding open-vm-tools to core group

Nicolas Mailhot nicolas.mailhot at laposte.net
Fri May 3 11:30:42 UTC 2013


Le Ven 3 mai 2013 01:46, Adam Williamson a écrit :

> I don't really hate the 'let's just install it everywhere and make sure
> it doesn't run unless it's necessary' approach, but it is kinda lazy
> engineering, and it *does* waste space on those small-space cases Peter
> is always reminding us about. Especially if this stuff goes in core.
>
> It seems like the thing to do would be to ask anaconda if it's
> feasible / desirable to make the installation of this stuff contingent
> on the environment.

Well, this is what I call lazy engineering: detect hardware at install
time, assume it never changes, and ask users to reinstall from scratch
whenever they move systems (or hunt-the-third-party-bits-on-the-internet à
la windows 95).

To do it properly you don't need just an anaconda workaround but some sort
of boot-time detection, that will require network access to repos to work,
and will quickly spiral into such complexity that makes it quite
unpalatable. Hardware support (which means drivers and associated tools)
should just be preinstalled for common hardware, and vmware passed the
"common" level a long time ago (people take existing systems and hack up
from them disposable vms all the time nowadays).

Regards,

-- 
Nicolas Mailhot



More information about the devel mailing list