<flokli>
damjan: you probably also need dev for headers, so you?
<flokli>
If it generally makes sense to build this with systemd for startup notification and logging, I'd just call the input systemd, and tolerate it being set to null.
<flokli>
I'm not yet really sure on the long-term story of this.
<flokli>
Personally, if it's only for the journal protocol and signalling readyness etc, I'd prefer if that protocol were stable, and there were a somewhat simple library implementing only these bits.
das_j has quit [Ping timeout: 272 seconds]
hexa- has quit [Ping timeout: 272 seconds]
das_j has joined #nixos-systemd
hexa- has joined #nixos-systemd
<damjan>
flokli: the sd_notify interface is stable and easily implemented. but you never know what apps will use :)
<damjan>
the journal interface OTOH is more complex
<flokli>
yeah
<damjan>
and yes, I do have the 'dev' too, was just wondering in general