Post by @ska@social.treehouse.systems

@ska@social.treehouse.systems

2026-10-20 17:47 UTC

@cazabon@mindly.social I was calling Lennart out in one of his threads where he announced his great solution to reduce the number of systemd's dependencies: put them behind a dlopen(), and then ldd won't show them! (I wish I was joking.) His answer was, as usual, a bad faith series of deflections and DARVOs and a lack of any kind of technical argumentation. And he said, allegedly jokingly, that s6 was a dependency hog because it was linked against 3 separate shared libraries (which is true for s6-svlisten, if you link all the components dynamically). You can find our exchange by foraging in my profile if you can be bothered to, but be warned that the discussion really is as technically empty as I summed up. The best part of it is the young wild boar picture I posted at the end.

Replies (1)

@daemonspudguy@app.wafrn.net 2026-10-20 21:02

@cazabon@mindly.social @ska@social.treehouse.systems Just for good measure I went and checked how many declared package dependencies there are for the main s6 package as provided on Artix Linux. There are currently exactly 3: execline, glibc, and skalibs. Meanwhile on Arch Linux (this is as fair a comparison as I can do and is in no way scientific), the latest package of systemd has 72 required dependencies, most of them are considered make dependencies, and 17 opinional dependences for a total of 89 dependencies. I wonder which one has more dependencies. To be fairer, s6-rc adds one make dependency, that being git. There's probably a considerably more reliable way to calculate this than counting by hand but that's what I did using the package repositories online because I'm at my phone right now.

Open ##5446157