ChanServ changed the topic of #nixos-systemd to: NixOS <3 systemd | https://jitsi.nixcon.net/systemd | Next meeting 08.12.2020 14:00 UTC (every two weeks)
asymmetric_ has joined #nixos-systemd
asymmetric has quit [Ping timeout: 256 seconds]
asymmetric_ is now known as asymmetric
<arianvp>
dlopen considered evil
<arianvp>
honestly why does go-systemd dlopen?
<arianvp>
.-.
<arianvp>
I guess some parts of its api don't need libsystemd; like socket activation
<arianvp>
but... in that case make that a separate library :/
<arianvp>
i dont understand go people . never will
<V>
dlopen considered evil indeed
<V>
failure at runtime is a terrifying thing
<andi->
dlopen only if optional for a feature
<andi->
but if your feature breakes without it... don't dlopen
<flokli>
I don't know the go compiler enough… but apparently all the CGO stuff is only ever used when /reading/ from the journal via libsystemd
<flokli>
so as long as I don't use that particular code, I don't propagate a dependency to libsystemd, do I?
<flokli>
so what's the problem with just keep linking as they did before?
<flokli>
I mean, if you pull that code in, you probably need libsystemd anyways if you want it to succeed
<flokli>
and dlopen all the things doesn't solve this, just moves it from compilation error to runtime error