If every upstream developer includes an option --with-systemd to make
their code work reliably with it, then all Debian package developers
will use the option without questioning if it is actually necessary.

Eventually, the switch packagers and developers will forget what was
actually being done by --with-systemd and it will become a default
configuration. The opposite option of --without-systemd may appear for
some of those applications where the developers can be bothered to cater
for non-systemd operating systems. Either way, systemd will infect as
many application packages as it can to make the process of removal later
too daunting or too time consuming a task to actually do.

-Vince-

On 12/07/17 06:18, Brad Campbell wrote:
> On 12/07/17 02:35, Dragan FOSS wrote:
>> On 07/11/2017 05:28 PM, Enrico Weigelt, metux IT consult wrote:
>>> make it crystal clear: fuck off the
>>> upstream.
>>
>> Do you want to say that devuan users do not need any upstream that
>> recommends systemd?
>> For example, Postgresql?
>> ***
>> With PostgreSQL 9.6 or newer, it is recommended to build with
>> --with-systemd and use the unit file shown in the documentation...
>> ***
>> https://wiki.postgresql.org/wiki/Systemd
>
> I read that page but my interpretation is different to yours.
>
> I read it as "If you want to run PG 9.6 or newer with systemd, use this
> option and the unit file we include. If you want to run an older version
> the recommended approach is to write a unit file using Type=forking and
> use pg_ctl for ExecStart and ExecStop."
>
> There is absolutely nothing there that is mandating systemd in any way,
> shape or form. They've just included code to make it behave better with
> systemd if that is how you choose to build it.
>
> Did I miss something or are you fearmongering?
>
> Brad
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng