Why would it need a home? I assume it is configured via /etc/ not via /home.

Like sddm, dm maybe want to write config, to home, to remember last logined session. Like last time, user login into sway, I want to make my dm to know, oh , the user login to sway last time, and put sway the first.

Greetd is a base for a lot of dm, and dm always want to let people can configure its appearance, and greetd has an ability to pass environments to session, then I can make a configure page, to let people configure their enviroment variables and etc for special desktop.

All of these need a writable dir, so it needs a home like sddm.

sddm write a config to remember which dm user login into lasttime, and the language user use. so if there is not a writable directory, these ability will be hard to impl

Like Now I am making a qmldm base on greetd, I like sddm very much, so I also want to write some config, but now greetd on arch does not has a home

Both sddm and gdm use a writable home to storage messages, for example in /var/lib/sddm/ there will always be a state.conf, the content is like

```
[Last]
User = user

Session=sway
```

For a gui dm, if is very useful to remember the last session

This is extra functionality that currently does not exist in greetd? Have you discussed adding this extra functionality with upstream greetd? Upstream can add a sysuders.d snippet including specifying a home directory. Upstream could also add a state directory to the service file it ships which I believe would meet your needs. Is it not premature for the Arch package to be changed at this point?

greetd just handle login, and it is just a daemon. these actions is done by dm,

I am talking about greetd itself and its impliments like greetd-gtk, they are like lightdm and lightdm-gtk.

and in the repo of upstream, there are even no sysuders.d sinppet.. this file is added by packager..so do archlinux packagers want the suggestion by developer?

and greetd-gtk or etc are just programs run with user `greetd`, if there is no home, they cannot write anything. greetd-gtk is the front-end of greetd, they talk through unixsocket

and if start fontend with some dm, like river, river required to wirte something to home. but if there is no home, river cannot configure itself, so this is another problem.. gui frontend always need to write some config.

even lightdm itself just need config under etc, but its impliments do not, they configure themself when they are running

Sorry, I found that greetd can use other user to start, so I just need to create a new user, and use that user to start is ok. so do not need archlinux to repackage it. sorry very much

> maybe want to write config

maybe??? So currently, there's no actual point to this feature request...

Also, "because sddm and gdm do it" is not a valid reason.