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.
Thanks
David
On 02/27/2015 06:23 PM, james machado wrote:
David,
Why would you make a routing daemon dependent on a specific init system?
James
On Thu, Feb 26, 2015 at 2:34 PM, David Jorm <[email protected]> wrote:
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 this
spec file includes:
%global _hardened_build 1
Which automatically adds security hardening compiler flags.
Thanks
David
