On Thu, Jan 28, 2016 at 01:21:07PM +0000, Rainer Weikusat wrote: > richard lucassen <[email protected]> writes: > > Daniel Reurich <[email protected]> wrote: > > > >> > I'm still running Debian but with the angband.pl repositories and > >> > this marks another stage of being unable to avoid libsystemd0 in > >> > Debian. > >> > >> Not yet, but it's noted and I'll work on that next week once work has > >> settled down a bit... > > > > I'm not a programmer, maybe I'm saying something incredibly stupid, so > > please don't shoot me, but wouldn't it be a better idea to build a > > Devuan libsystemd0 that fakes the real libsystemd0 instead of adapting > > all programs to not using libsystemd0? > > This depends on how the library is being used. If it's just a spurious > dependency, a simple dummy will work in place of it. But this usually > won't be the case as the express purpose of libsystemd is to enable code > to be written/ changed to use systemd APIs instead of the facilities > systemd uses to implement these by providing a second implementation of > the systemd API in a library. > > For the given case, this means that the Debian package will enable X > server systemd support unconditionally when building for a Linux-based > system and the corresponding facilities are either supposed to be > provided by system-alpha, the set of programs controlling the system, or > by systemd-quisling, the secondary (and presumably somewhat sub-par) > implementation in the library. > > Until Debian formally ejects it's non-Linux sub-projects, any such > attempts are restricted to being more-or-less elaborate nuisances > created by people with too much time on their hands.
Do you mean "ejects its non-systemd subprojects"? Or do I misunderstand you? -- hendrik _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
