Matthew Miller (mattdm(a)fedoraproject.org) said:
On Tue, Oct 09, 2012 at 10:23:05PM -0400, Bill Nottingham wrote:
> A cleaner way to do it is to *package* it in in a spin specific package that
> gets pulled in by the appropriate spin early in the transaction so it's
> there for all services. So, for example, fedora-release requires:
Right, so, the problem is: the reason we're doing all this is so that cloud
init won't default to on-when-installed, so that if people install it by
accident, they won't accidentally get... cloudinited.
But if we have a cloud-preset package that turns on cloud-init when
installed, we've just moved the problem up one layer of abstraction with no
particular gain that I can see, unless you value obfuscation for its own
sake. :)
The idea is that the cloud-preset package would only be on the cloud spins.
If you're installing random preset files from the repo, or, god forbid,
*everything* including conflicting presets, you get to step on all the sharp
pieces, and I hope you're up-to-date on your shots.
Bill