Created attachment 371246 [details] Build log Long story short, in systemd-209 the libsystemd-* libraries were removed and replaced with single libsystemd. We install compatibility libsystemd-*.pc pkg-config files, so apps using pkg-config are not affected (yet :)). Since sane-backends tries to link libsystemd-daemon directly, it fails terribly with >=systemd-209. The possibilities are: 1. use pkg-config to query libsystemd-daemon -- compatible with all versions but at some point we will be removing compat pkg-config files, 2. use pkg-config to query libsystemd, fallback to querying libsystemd-daemon -- future- and backwards-compatible, 3. just use libsystemd, and dep on >=systemd-210 in the ebuild (we didn't add -209). Preferably, always use pkg-config :). If you need any help, please let us know.
I suppose this will also require a patch to stable eventually, since stable will fail to build against version 209?
(In reply to Chris Brannon from comment #1) > I suppose this will also require a patch to stable eventually, since > stable will fail to build against version 209? Either that, or proper <systemd-209 dep. We don't expect systemd-210 to go stable anytime soon though :).
Would be nice to know how other distributions plan to handle that (to not reinvent the wheel or to not spend efforts in some solution that will finally be rejected by upstreams because other distros choose to go in other direction)
Most of other distros don't have much of a problem since they need to support one version only -- the one they link to :).
Fixed in sane-backends-1.0.24-r3. Also going to commit to stable with a dependency on <sys-apps/systemd-209, since I realize that this is safe because of the compatibility symlink.
