[ISSUE] elogind systemd dependencies

[ISSUE] elogind systemd dependencies

[dreamer1234]

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

New issue by dreamer1234 on void-packages repository

https://github.com/void-linux/void-packages/issues/26177

Description:
The elogind package is dependant on systemd.
Looking at the template:

[code]
post_install() {
        ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd.pc
        ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd-logind.pc
        ln -sr $DESTDIR/usr/include/elogind $DESTDIR/usr/include/systemd
        vinstall ./src/systemd/sd-id128.h 644 usr/include
        vinstall ./src/systemd/_sd-common.h 644 usr/include
        vinstall $FILESDIR/elogind.wrapper 755 usr/libexec/elogind
        vmkdir usr/lib/dracut/dracut.conf.d
        echo "install_items+=\" /usr/libexec/elogind/elogind-uaccess-command \"" >> ${DESTDIR}/usr/li
b/dracut/dracut.conf.d/elogind.conf
        vsv elogind
}
[/code]

Which seems a bad desing, since we are introducing systemd dependencies on a non systemd distribution. 

Re: elogind systemd dependencies

[ofiala-a51]

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

New comment by ofiala-a51 on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723223181

Comment:
This should be expected since elogind is just systemd's logind fork that doesn't depend on the whole systemd itself. If you are opposed to using systemd components in your system like many of us, you should consider using an alternative -- see #24580. You can get it and compile it yourself while the PR is waiting to merged. Please note, that you might have to recompile everything that depends on libelogind to support libseat instead (this should hopefully be slowly fixed by subsequent PRs once #24580 gets merged).

Re: elogind systemd dependencies

[ofiala-a51]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

New comment by ofiala-a51 on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723224040

Comment:
Also note, that the name `libsystemd` is for compatibility reasons. The package's name is `libelogind` and only contains the portions required to work w/ elogind.

Re: elogind systemd dependencies

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723226023

Comment:
i see 3 issues with this issue:

* the `elogind` package doesn't actually depend on `systemd` at all
* github uses markdown, not bbcode, please use ``` instead of `[code]` and `[/code]`
* and nothing in that `post_install` function you're quoting actually introduces any dependency on systemd, the name is simply there for compatibility with software that expects there to be a systemd-logind under that name.

essentially the same as `libressl` installing `/usr/bin/openssl` as a compatibility wrapper. that doesn't mean it "depends on" `openssl`, on the contrary it allows other things to *not* depend on it. same applies here, due to the compatibility stuff installed by `elogind` we make it so we don't have to install systemd-logind but still support software that's "used to" that.

Re: elogind systemd dependencies

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723226023

Comment:
i see 3 issues with this issue:

* the `elogind` package doesn't actually depend on `systemd` at all
* github uses markdown, not bbcode, please use ``` instead of [code] and [/code]
* and nothing in that `post_install` function you're quoting actually introduces any dependency on systemd, the name is simply there for compatibility with software that expects there to be a systemd-logind under that name.

essentially the same as `libressl` installing `/usr/bin/openssl` as a compatibility wrapper. that doesn't mean it "depends on" `openssl`, on the contrary it allows other things to *not* depend on it. same applies here, due to the compatibility stuff installed by `elogind` we make it so we don't have to install systemd-logind but still support software that's "used to" that.

Re: elogind systemd dependencies

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723226023

Comment:
i see 3 issues with this issue:

* the `elogind` package doesn't actually depend on `systemd` at all (and couldn't even if it wanted to since `systemd` isn't a void package)
* github uses markdown, not bbcode, please use ``` instead of [code] and [/code]
* and nothing in that `post_install` function you're quoting actually introduces any dependency on systemd, the name is simply there for compatibility with software that expects there to be a systemd-logind under that name.

essentially the same as `libressl` installing `/usr/bin/openssl` as a compatibility wrapper. that doesn't mean it "depends on" `openssl`, on the contrary it allows other things to *not* depend on it. same applies here, due to the compatibility stuff installed by `elogind` we make it so we don't have to install systemd-logind but still support software that's "used to" that.

Re: elogind systemd dependencies

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/26177#issuecomment-723226023

Comment:
i see 3 issues with this issue:

* the `elogind` package doesn't actually depend on `systemd` at all (and couldn't even if it wanted to since `systemd` isn't a void package)
* github uses markdown, not bbcode, please use ``` instead of [code] and [/code]
* and nothing in that `post_install` function you're quoting actually introduces any dependency on systemd, the name is simply there for compatibility with software that expects there to be a systemd-logind under that name.

essentially the same as `libressl` installing `/usr/bin/openssl` as a compatibility wrapper. that doesn't mean it "depends on" `openssl`, on the contrary it allows other things to *not* depend on it. same applies here, due to the compatibility stuff installed by `elogind` we make it so we don't have to install systemd-logind but still support software that's "used to" that.
same would apply to `eudev[-libudev]` btw.

Re: [ISSUE] [CLOSED] elogind systemd dependencies

[q66]

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Closed issue by dreamer1234 on void-packages repository

https://github.com/void-linux/void-packages/issues/26177

Description:
The elogind package is dependant on systemd.
Looking at the template:

[code]
post_install() {
        ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd.pc
        ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd-logind.pc
        ln -sr $DESTDIR/usr/include/elogind $DESTDIR/usr/include/systemd
        vinstall ./src/systemd/sd-id128.h 644 usr/include
        vinstall ./src/systemd/_sd-common.h 644 usr/include
        vinstall $FILESDIR/elogind.wrapper 755 usr/libexec/elogind
        vmkdir usr/lib/dracut/dracut.conf.d
        echo "install_items+=\" /usr/libexec/elogind/elogind-uaccess-command \"" >> ${DESTDIR}/usr/li
b/dracut/dracut.conf.d/elogind.conf
        vsv elogind
}
[/code]

Which seems a bad desing, since we are introducing systemd dependencies on a non systemd distribution.