Skip to main content ↑ ↓
Topic: Artix without compulsory elogind (Read 2929 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Artix without compulsory elogind

Reply #15 –
Quote from: Nostos – on
Then make it optional. I'm using BSPWM. Why should I have to use something that I have no use for just because the next guy *might* want to use KDE?

Because Artix maintainers have limited resources and find that allocating them towards compiling multiple packages twice is not a good idea. In fact, they've already made elogind optional to the extent that is possible without incurring in this penalty, and there are many people running Artix without a trace of elogind in their process table. Libelogind isn't the full-fledged daemon.

If you find even having the library on your filesystem offensive, unfortunately Artix is not for you (and won't be for the foreseeable future). Distros like Gentoo (or hey, KISS Linux, that one distro with the bare minimum needed to run Firefox!) are better suited for that.
 

Re: Artix without compulsory elogind

Reply #16 –
After libudev-zero i think it is possible to create some lib to translate elogind calls into consolekit and seatd ones (or maybe even some dummy lib so that software won't complain). The question is, do we have any good enough anti-elogind coders who could implement that?
ARMtix

Re: Artix without compulsory elogind

Reply #17 –
Quote from: phoenix_king_rus – on
After libudev-zero i think it is possible to create some lib to translate elogind calls into consolekit and seatd ones (or maybe even some dummy lib so that software won't complain). The question is, do we have any good enough anti-elogind coders who could implement that?
The real solution would be convincing the developers of programs who without any real reason whatsoever integrate with systemd or elogind to stop doing that.

Alternatively, one can just not use such programs. Artix is a distro which includes "desktop" software: GNOME, KDE and their derivatives. From an organizational standpoint, it is not practical to maintain two separate "flavors" for every package which potentially depends on elogind. As suggested by @artoo, source-based distro is a better solution. It doesn't have to be Gentoo, as well. For example there is Linux From Scratch.

Re: Artix without compulsory elogind

Reply #18 –
Quote from: phoenix_king_rus – on
After libudev-zero i think it is possible to create some lib to translate elogind calls into consolekit and seatd ones (or maybe even some dummy lib so that software won't complain). The question is, do we have any good enough anti-elogind coders who could implement that?

Well I think seatd currently has what you're looking for. It picks up logind API calls and handles them appropriately (provided it is compiled with logind support which is is on Artix which requires libelogind). The main thing is that elogind is more than just merely a library and does some other things as well. One of these is acl's for groups which I've never gotten around to duplicating.

Re: Artix without compulsory elogind

Reply #19 –
There're some binary distros which don't have systemd and elogind. Slackware, pclinuxos and of coz obarun are 3 of them.

I am not against using elogind. As long as the init system just "inits" the system right, I am OK.