Skip to content

Move greetd config to data and add autologin example#182

Merged
samcday merged 2 commits intosamcday:mainfrom
agx:auto-login
Mar 2, 2026
Merged

Move greetd config to data and add autologin example#182
samcday merged 2 commits intosamcday:mainfrom
agx:auto-login

Conversation

@agx
Copy link
Collaborator

@agx agx commented Mar 1, 2026

Having it in data eases finding it and people ever so often wonder how to auto log in.

There's additional copies for apline and fedora which we could get rid of if we use e.g. meson and add --vt and --greetd-user options but that could also be a follow up.

agx added 2 commits March 1, 2026 13:40
This comes up ever so often.

Signed-off-by: Guido Günther <agx@sigxcpu.org>
This comes up ever so often

Signed-off-by: Guido Günther <agx@sigxcpu.org>
@samcday
Copy link
Owner

samcday commented Mar 2, 2026

Having it in data eases finding it and people ever so often wonder how to auto log in.

Awesome, thanks 👍

There's additional copies for apline and fedora which we could get rid of if we use e.g. meson and add --vt and --greetd-user options but that could also be a follow up.

I still find the idea of wrapping our Cargo.toml in Meson kinda icky. Maybe squeekboard traumatized me and now I'm convinced I can never love again, idk.

At any rate...

What you're describing could still be achieved in a straightforward manner with some build.rs shenanigans, no? i.e at build-time you look for PHROG_GREETD_VT/etc and spit out a generated greetd.toml in $CARGO_TARGET_DIR or somesuch.

I maintain the Fedora and Alpine packaging, so if you wanted to align Debian's upstream packaging on this convention and we make sure we reuse exactly the same 🐸ified greetd.toml, I'd love that and would (well, ask the 🤖 xD) to do that build.rs thing and formalize it.

@samcday samcday merged commit 5faedb4 into samcday:main Mar 2, 2026
15 checks passed
@agx
Copy link
Collaborator Author

agx commented Mar 2, 2026

I still find the idea of wrapping our Cargo.toml in Meson kinda icky. Maybe squeekboard traumatized me and now I'm convinced I can never love again, idk.

We wouldn't need to do that. They can be entirely separate or build.rs could call meson (but then passing command line options becomes harder)

and we make sure we reuse exactly the same 🐸ified greetd.toml

Issue here is that different distros use different users which is hard to change (for little gain upstream).

I think shipping a reference config that downstream can grab and potentially patch is better than having everyone guess so the whatever works best for you works for me here to get rid of the duplication. We could also detect $distro at build time and put out the right params in build.rs ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants