Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gdm: enable smooth transition with plymouth. #28570

Merged
merged 1 commit into from
Feb 8, 2021

Conversation

nuclearforg
Copy link
Contributor

Support for smooth transition was disabled years ago, when plymouth wasn't in the Void repo. gdm checks whether plymouth can be pinged at run time so that no hard dependency is required.

General

Have the results of the proposed changes been tested?

  • I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
  • I generally don't use the affected packages but briefly tested this PR

-Dsystemd-journal=false -Dinitial-vt=7 -Dwayland-support=true
-Dselinux=disabled -Dlibaudit=disabled
-Dsystemdsystemunitdir=/tmp -Dsystemduserunitdir=/tmp"
hostmakedepends="dconf gettext itstool pkg-config"
makedepends="accountsservice-devel elogind-devel gettext-devel glib-devel
iso-codes libSM-devel libcanberra-devel nss-devel pam-devel upower-devel"
iso-codes libSM-devel libcanberra-devel nss-devel pam-devel upower-devel
plymouth-devel"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it checks for the plymouth library at configure time (I could find this line), but doesn't link against it? At least I couldn't see anything about it in the CI log...

Just wondering what it is that it does with the library, and if we need any sort of warning about plymouth library revbump or such.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does absolutely nothing with the library, yet it requires ply-boot-client.pc to be present at configure time. Code just spawns plymouth binary and that's all.

The quirky logic comes from a patch written by Fedora devs 11 years ago. My best guess is that it was upstreamed without anyone knowing what it really did.

@ericonr ericonr merged commit 5573481 into void-linux:master Feb 8, 2021
@nuclearforg nuclearforg deleted the gdm-plymouth branch March 18, 2021 22:06
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants