[PATCH] RPM spec file with systemd integration
hvgeekwtrvl at gmail.com
Fri Feb 27 09:39:54 CET 2015
On Fri, Feb 27, 2015 at 12:29 AM, David Jorm <djorm at corp.iixpeering.net> wrote:
> Good question. My intention is not to make BIRD dependent on a specific init
> system, but to offer a choice. That is why my patch does not overwrite the
> existing bird.spec file, but instead provides a new bird-systemd.spec file
> as an alternative. I understand that systemd is controversial, and I do not
> agree with the model of "nuke sysv init and pave with systemd". I do,
> however, support choice.
I'm all for choice as well. Trying to take the controversy out of it,
let me try to rephrase. What benefit(s) is/are gained by making BIRD
dependent on systemd that is not available without the dependency?
Conversely what breakage happens by making it a dependency?
> On 02/27/2015 06:23 PM, james machado wrote:
>> Why would you make a routing daemon dependent on a specific init system?
>> On Thu, Feb 26, 2015 at 2:34 PM, David Jorm <djorm at corp.iixpeering.net>
>>> Hi All
>>> The attached patch provides an RPM spec file with systemd integration,
>>> rather than sysv init. I have tested it on Fedora 20 and 21. Note that
>>> spec file includes:
>>> %global _hardened_build 1
>>> Which automatically adds security hardening compiler flags.
More information about the Bird-users