LoginKit supposedly implements parts of the libsystemd IPC against DBus while passing the remainder of logind function calls back to ConsoleKit2. LoginKit only covers the "inhibit()" function while everything else is covered by ConsoleKit2, for now at least. In LoginKit it only uses what the author felt was needed, nothing else.
There's no real need to reimplement it as a system shared library. Just strip out the parts needed by your project that supplements the parts of systemd you are aiming to replace, and use the stripped down libsystemd internally within your project(s). This way you also compartmentalize out libsystemd into it's various functions and avoid unused parts. -Jim Date: Wed, 6 May 2015 18:38:03 +0300 From: d...@dimakrasner.com To: dng@lists.dyne.org Subject: Re: [Dng] Is it useful to create a .so file to replace functions imported from libsystemd & Co.? On Wed, 6 May 2015 06:58:41 +0000 Edward Bartolo <edb...@gmail.com> wrote: > The exercise is to search for these functions in systemd's source code > and create a .so file with only the required functions. The functions > can also be reimplemented, but that takes more time than simply > stripping the required functions. This is a complicated task, as many libsystemd functions actually perform IPC against logind, so you have to either: - Re-implement both logind and libsystemd - Make your libsystemd work with ConsoleKit or something, instead of logind I tried both approaches and it's incredibly complex. -- Dima Krasner, dimakrasner.com _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
