loginkit when built produces some libraries, named as libsystemd.so, libsystemd-login.so and so on.
I strongly suggest to avoid to name them this way, and to rename the libraries as libloginkit.so, libloginkit-login.so and so on, and then symlink them to libsystemd.so libsystemd-login.so and so on to compatibility if needed.
loginkit binaries should link to libloginkit- .so shared objects, and symlink from libsystemd- .so should be provided only for things like gdm or any other piece of software that ask for systemd libraries for compatibility.
What about the soname? Linking pam_loginkit against libloginkit-login isn't good enough, because applications look for the libsystemd-login.so.0 soname. I was thinking, maybe all libraries should be built in two variants - one with libsystemd- .so.0 and another with libloginkit- .so.0.
Then, we can move all systemd compatibility libraries and headers to libloginkit-compat and libloginkit-compat-dev. The former will provide libsystemd-*.
A symlink from libsystemd-login.so.0 to libloginkit-.so.0 should be enough, this way we of course needs to have conflicts line and provides name to make the package resolve right dependency, or we will have to patch things to link against libloginkit.
Status changed to closed