Le 13/06/2015 01:15, Laurent Bercot a écrit :
Encouraging daemon writers to use another API and providing a wrapper
to make daemons using the simpler API work with the sd_notify mechanism
is clearly the better ideological solution, and also technologically
preferable because more compatible with other notification frameworks;
but it's harder, because it requires communication with daemon authors,
and the systemd proponents have more communication power than we do
(read: $$$). But I think authors can be convinced if we show that our API
is simpler to use and will work under any framework, systemd included.
Yes, daemon writers are good-willing developpers; they want their
software to serve as many users as possible; and users install distros.
This gives power to the distros. But if someone provides them with a
KISS readyness-signaling method, along with a systemd wrapper, then they
can satisfy RedHat's requests at no cost.
The question now is who will develop, maintain and package this
wrapper? Will Devuan be the official developper of
"Systemd-Readyness-Wrapper", or can anyone convince Openssh or who else
to take the job? Or are the daemon's developper powerfull enough to tell
RH "do it yourself."?
Didier
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
