Zbigniew Jędrzejewski-Szmek wrote:
They *could*, but most likely not in a fashion that is flexible
enough.
Essentially, shipping presets in the package itself is equivalent to
statically enabling or disabling the services contained in that
package (*). Presets are useful to provide different defaults for
different Fedora flavours. In the case at hand, cloud setup services,
it would be reasonable to include a preset to enable them, but only in
Cloud variants. If the user installs one those packages on
Workstation/KDE/whatever, it makes sense to default to "off".
Requires: (proprietaryware-preset-cloud if fedora-release-cloud)
Any rpm that is installed already gets effectively full control over
the system (directly without any effort, if scripts are not disabled,
and they must not be for presets to work). So "name hijacking" would
be an unnecessary detour at that point.
True. Still, the potential for name conflicts is there.
Kevin Kofler