#2: How to handle systemd service activation defaults in EPEL7 -----------------------------+---------------------------- Reporter: orion | Owner: epel-wranglers Type: task | Status: new Priority: major | Milestone: EPEL-7 Component: Policy problem | Version: Resolution: | Keywords: -----------------------------+----------------------------
Comment (by stahnma):
I'm against a new package that epel-release depends upon.
Most people don't install epel-release with yum - at least in my experience. They wget it or rpm -Uvh http://blahblah. This means that dependency resolution may not be in play at this time. I think this would break workflows for testing, and validation. (I know it would break what we do at Puppet Labs).
As for the second option, I'd like to see the exact differences in a spec file to see how intrusive it is.
From an ecosystem perspective, I think having no presets for EPEL packages feels the most right, but my perspective could be pre-systemd and therefore out of date.