Hi Sean, On Tue, Dec 17, 2024 at 10:42:37AM +0800, Sean Whitton wrote: > On Sun 15 Dec 2024 at 06:23pm +01, Helmut Grohne wrote: > > Whether logging is available no longer is a boolean. A container > > runtime can provide a /dev/log service by forwarding to an external > > logging service. Many systems now use journald as their only logging > > daemon, but journald can also cooperate with another logging daemon. > > Removing dependencies on system-log-daemon should be seen as a > > recognition that the availability of a logging daemon can no longer > > reasonably be expressed using the dependency system. Additionally, > > most log message producers fail gracefully in the absence of a log > > consumer by skipping logging. > > That's a lot of additional text :) We should probably keep the options > all about the same length?
We have a history of augmenting resolutions with rationales. I see that additional text as a rationale that is appended outside of the resolution in case it passes. For instance in #914897 our rationale is far longer. Whilst we are voting on the "what" (and all of the proposed solutions rightly focus on the "what", thanks Matthew), answering "why" is quite important for gathering acceptance. When I read a resolution, I very much want to have a basic understanding of "why". The split into resolution and rationale allows the reader to decide whether they're interested. I'd also welcome rationale texts for the other proposed resolutions. Helmut
