Noé Lopez <[email protected]> writes:

> Hi GNOME team,
>
> In [1], GNOME recently announced some new dependencies on systemd for
> release 49.
>
> Firstly, GDM now depends on userdb to dynamically allocate user accounts
> for showing multiple GDM at once. However, there is an alternate code
> path for elogind that means we can preallocate gdm-greeter-N
> accounts. This should not be very complicated to do.
>
> Secondly, gnome-session (responsible for starting user services) is
> going to use systemd too. So we need to replace it with a Shepherd
> implementation.
>
> Lastly, they will also replace AccountsService with userdb. But that is
> for GNOME 50.
>
> I can start to look into replacing gnome-session with a Shepherd
> implementation for our current GNOME, so it will be already done once we
> get to 49. (will also help us debug GNOME’s services better)
>
> What do you think?
> Noé
>
> [1] https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/

Hi everyone,

Here with many good news :)

Firstly, I just released version 0.6 of gnome-session-shepherd. Which
can now function as a replacement to upstream’s gnome-session. It is
still lacking a few non-essential features and documentation before
releasing 1.0.

Secondly, I have made contact with the Gentoo people which have the same
issues as us. They are very nice and we are able to share ideas and
knowledge.

Thirdly, elogind allegedly (source Gentoo people) contains userdb
already, but had a few broken parts. Which means that we will be able to
just upgrade it once the related pull request is merged.

Fourthly, I met a cool hacker that seems to churn out independent
implementations for systemd modules for fun. And we will probably need
some of those in the future. See <https://gardenhouse.pinkro.se/>.

Lastly, the bad news is that GNOME now only mostly ships systemd
services, so we can try to make shepherd load those or we have a bunch
of patching on our hands.

That’s it! Have a great week-end,
Noé

Attachment: signature.asc
Description: PGP signature

Reply via email to