On Mon, Nov 17, 2014 at 12:54 AM, Walter Dnes <waltd...@waltdnes.org> wrote: > On Sat, Nov 15, 2014 at 04:11:56PM -0500, Rich Freeman wrote >> >> USE=systemd simply means to enable support for systemd, not that it is >> running. Generally stuff like this should be a matter of >> configuration, not build options. >> >> Otherwise your life as a Gentoo user would be a living nightmare when >> you look at how many profile use flags there are. > > There are already some situations where 2 programs cannot co-exist, > e.g. 2 MTAs. This may be a similar situation in principle. A system > daemon may operate differently under openrc than systemd. When I run > > emerge -pv syslog-ng > > I see that a "systemd" USE flag exists, but not an "openrc" USE flag. > I think that's the root of the problem. The default is to support > openrc. When the ebuild sees sees the "systemd", it assumes you're not > running openrc. Maybe the solution for syslog-ng is to add an "openrc" > USE flag. Build in support for whichever flag is set. When > experimenting, people might want to set both "openrc" and "systemd" USE > flags for syslog-ng. If systemd users have to set the "systemd" flag > for some ebuilds, I have no objection to setting the "openrc" USE flag > in make.conf.
Is the "systemd" USE flag an actual syslog-ng compilation option or it is a flag to generate systemd units when syslog-ng is installed? If it's the latter, an "openrc" flag would be a no-op, unless someone wants the option to set "-openrc" and not have a runscript installed.
