Move greetd config to data and add autologin example#182
Move greetd config to data and add autologin example#182samcday merged 2 commits intosamcday:mainfrom
Conversation
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>
Awesome, thanks 👍
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 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. |
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)
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 ? |
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
--vtand--greetd-useroptions but that could also be a follow up.