Comment by jwrteqhrwj
12 days ago
skalibs version 2.14.0.0 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the skalibs library.
s6 version 2.12.0.0 or later. It's a run-time requirement only, to run the nsssd service (and can be done without if you have a suitable replacement for s6-ipcserver).
I love that the anti-systemd crowd is implementing their own systemd.
ska (and djb) libs have its own little world which, in some aspects, is weirder than systemd.
A most striking example is their time approach - they refuse to acknowledge 64-bit timeval and claim "those APIs will become obsolete in 2038" [0]; instead, they promote the TAI time, which is uses Unix epoch, except with bit 63 set and adjusted by leap seconds offset (whose value changes every few years or so, so old code needs to be patched or all timestamps would be a few seconds off). And this is not just internals; it's visible to users for example in log file names [1]
Now, I don't care if it's TAI or UTC, but I do think the working well with others is very important. And choosing a timestamp which is incompatible with basically every other piece of software out there is.. suboptimal.
[0] https://skarnet.org/software/skalibs/libstddjb/tai.html
[1] https://skarnet.org/software/s6/s6-log.html
well, of course to reach feature parity you have to implement it somehow. the question how they do it is a different can of worms.
i am glad they stopped complaining and do their own thing. i mean, this is opensource and free software about.