deb packages conflicts and provides
I see in the control file you set conflicts to systemd from libpam-loginkit binary package. Shouldn't it conflicts with libpam-systemd instead?
Same apply to other packages, a more carefull conflicts line is needed.
In the same time, we should add a "provides" line, for example in libpam-loginkit binary package a provides for libpam-systemd is probably needed, so, other packages with dependency to libpam-systemd can resolve it by installing this package.
That's not entirely correct - you cannot use libpam-loginkit against systemd. I'm not sure whether a "provides" field is the right thing to do, but you're the boss.
Make sense, as effectively libpam-loginkit isn't a drop-in replacement for all things that links against libpam-systemd.
Anyway, this would say that we will need to rebuild also gdm package and other packages using systemd-logind to add a dependency with preference on loginkit, and fix only the conflicts line without add the provides
Things don't link against libpam-systemd, they just assume the environment variables and the logind session it creates are in place. Yes - I think you're right. It will take some time to figure out which missing libpam-systemd need to be added to libpam-loginkit, though.
Once I get GDM to work (and let's hope I can make it) things will be easier on the dependencies front.
Yes, sorry, i was thinking on libs, but of course libpam-things are not what they link against. Anyway, i think that rebuild GDM and other things loginkit will support even for just add right dependencies ( where right would say add loginkit things ) and rename loginkit pam module to libpam-loginkit instead of libpam-systemd i think is the right way.
Status changed to closed